improv(ci): Inherited the secrets for update ssm workflow

[sdangol]

Summary

This PR allows the secrets to be inherited from the parent workflow to the Update SSM workflow to fix the issue during running the release workflow
The inheritance was previously updated because of a security finding.

Changes

Please provide a summary of what's being changed

• Reverted the explicit specification of secrets to use inherit keyword since the update parameter SSM would use secrets for each regions

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

Issue number: closes #4387

---

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.

[sdangol]

@sthulb One of the changes we did last time didn't succeed in the release pipeline today. This seems to be because of the secret(role) not being available to the workflow when used as a reusable workflow.
I've reverted the changes to use the inherit keyword. But, this would introduce a SonarQube finding about using inherit for secrets.
What do you suggest we should do?

[dreamorosi]

I've marked them as safe on SonarCloud - let's improve the explanation documenting what we're doing, why, and how we're addressing concerns rather than just saying "it's going to trigger SonarCloud findings".

[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