chore(parameters): update AWS SDK client type

[dreamorosi]

Summary

Changes

Please provide a summary of what's being changed

This PR is a second attempt at fixing the issue described in the linked issue, which is to make the usage of a client in the BaseProvider class optional.

The first PR updated the logic but omitted making the parameter optional in the types. This PR fixes that.

The PR also removes a 3rd party dependency on hashi-vault-js which was used in the examples, in favor of a much simpler and dependency free direct API call using fetch.

Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed

Issue number: closes #2400

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[leandrodamascena]

I'm going to review this tomorrow morning.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[leandrodamascena]

This PR looks good to me! Even though this is a simple example to show customers how to extend the parameter provider, I wouldn't show customers how to do this via HTTP call instead of Vault Client because customers need to deal with unseal, retry, certificate and so on, and using HTTP for that is super hard.

But it's just a comment! Approving.

[dreamorosi]

I hear you, but that was an unofficial client and it was bringing some transitive dependencies that were causing GitHub alerts, so for this I'll leave it as is for now.