Add example for Self provisioned AWS S3 or S3-compatible storage credential creation

[ramya-bangera]

1. What this PR does / why we need it:
   Add example for Self provisioned AWS S3 or S3-compatible storage credential creation

2. Which issue(s) this PR fixes

   Internal Jira ticket
   

3. Additional information
   This change adds example for creatingSelf provisioned AWS S3 or S3-compatible storage credential creation for data protection

4. Special notes for your reviewer

[vmwclabot]

@ramya-bangera, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 68b7195 must be signed by bangerar@vmware.com

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3b8edbd) 25.39% compared to head (8d2244a) 26.12%.
Report is 32 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #296      +/-   ##
==========================================
+ Coverage   25.39%   26.12%   +0.72%     
==========================================
  Files         155      161       +6     
  Lines       13591    14318     +727     
==========================================
+ Hits         3452     3740     +288     
- Misses       9982    10411     +429     
- Partials      157      167      +10     

see 15 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[shobha2626]

LGTM

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.