Ability to register S3 buckets as data sources

## Who will benefit?
Customer organizations that implement a robust data lake solutions involving onboarding data assets from S3 data source will benefit from this feature

## 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
Add the ability to onboard S3 data sources by collecting the details of S3 location as input. The capability is currently available in SMUS via UI. Atatching the screenshot:

## Acceptance Criteria
Within the data catalog section of SMUS project, users should have the ability to view and use S3 location onboarded via MDAA as a data souce.

## Examples
No

Start by inspecting the data catalog section and the existing MDAA data-source onboarding flow, then compare it with the S3 location capability shown in the SMUS UI screenshot. Confirm the required S3 location details and verify that an onboarded S3 source can be viewed and used in the SMUS project data catalog.

Written by the indexing model from the issue text.