MDAA_SMUS_Metadata_Forms_Feature_Request

## Problem Statement
Ability for users to create metadata forms and attach them to domains via MDAA.

## Who will benefit?
Customer organizations that implement a robust data lake solutions involving multiple accounts, projects, producers and consumers. Also, customers implementing a data-mesh or a hub spoke model of data producers and consumers involving multi-account/multi-region setup would benefit from this feature. Ability to attach metadata forms will enable customers enforce data governance standards across the producer-subscriber ecosystem

## Is this a sub-issue?
No

## What risks could this introduce?
A new feature/capability to be added. Do not see introducing new risks

## Proposed Solution
Provide users the ability to upload metadata forms that they create and upload from their local systems or referenced in S3 buckets. This approach follows the similar pattern to how Glue ETL jobs can be uploaded and referenced from the local file system.

## Acceptance Criteria
When the domain gets created, users should be able to login and see the metadata forms at domain level to be able to attach them to any particular asset. Attached is the screenshot of where the forms would show up in SMUS UI.

## Examples
No

Start by reviewing the existing domain and asset creation flows, along with the Glue ETL/S3 upload and reference pattern described in the issue. Done means users can view metadata forms at the domain level and attach a selected form to an asset in the SMUS UI.

Written by the indexing model from the issue text.