Purpose

This pull request introduces support for retrieving and utilizing flow metadata from the new Asgardeo V2 platform API (GET /flow/meta). It adds a new API client, comprehensive type definitions, and wires flow metadata into the core sign-in, sign-up, and sign-out button components. Additionally, it exposes the new API and types in the JavaScript package's public interface, and adds a configuration option for resolving themes from flow metadata.

New API and Type Definitions:

• Added a new API client function getFlowMetaV2 to fetch aggregated flow metadata from the Asgardeo V2 platform, including application/OU details, design configuration, translations, and registration flow status.
• Introduced extensive TypeScript types and enums for flow metadata, including FlowMetaType, ApplicationMetadata, OUMetadata, DesignMetadata, I18nMetadata, FlowMetadataResponse, and related theme configuration types in flow-meta-v2.ts.

Component Integration:

• Updated the base and public sign-in, sign-up, and sign-out button components in React to accept and propagate the new meta prop, which contains the flow metadata (or null if unavailable). This allows downstream consumers and custom render functions to access flow metadata. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]

Public API and Configuration:

• Exported the new API client and all related types from the JavaScript package's main entry point for external use. [1] [2]
• Added a resolveFromMeta option to the Preferences interface to allow theme resolution from the Flow Meta API when using Asgardeo V2.

Build and Scripts:

• Added new build scripts for building only the packages or samples directories, improving developer workflow.

Related Issues

• Resolve Consume the flow/meta endpoint of Thunder to reolve theme, i18n, etc. #369

Related PRs

• N/A

Checklist

• Followed the CONTRIBUTING guidelines.
• Manual test round performed and verified.
• Documentation provided. (Add links if there are any)
• Unit tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?