docs: fix auth secretRef in API docs

[mubarak-j]

Problem Statement

The API docs reference accessKeyID and secretAccessKey but looking at SecretStore CRD, it seems the correct field names should be accessKeyIDSecretRef and accessKeySecretSecretRef respectively.

Related Issue

Faced this validation error when using the example in API docs

error: error validating "secretstore.yaml": error validating data: [ValidationError(SecretStore.spec.provider.aws.auth.secretRef): unknown field "accessKeyID" in io.external-secrets.v1beta1.SecretStore.spec.provider.aws.auth.secretRef, ValidationError(SecretStore.spec.provider.aws.auth.secretRef): unknown field "secretAccessKey" in io.external-secrets.v1beta1.SecretStore.spec.provider.aws.auth.secretRef]; if you choose to ignore these errors, turn validation off with --validate=false

Proposed Changes

How do you like to solve the issue and why?

Checklist

• I have read the contribution guidelines
• All commits are signed with git commit --signoff
• My changes have reasonable test coverage
• All tests pass with make test
• I ensured my PR is ready for review with make reviewable

[paul-the-alien]

Greetings!
Thank you for contributing to this project!
If this is your first time contributing, please make
sure to read the Developer and Contributing Process guides.
Please also mind and follow our Code of Conduct.

Useful commands:

• make fmt: Formats the code
• make check-diff: Ensures the branch is clean
• make reviewable: Ensures a PR is ready for review

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[moolen]

Thanks for fixing this 🏅 ! i've stumbled over this a couple of times, too! Never took the time to fix it 😅

Much appreciated!