Updated Azure DevOps service connection instructions in README.md

[rchildress87]

Description

Replaced some inaccurate instructions, replaced all references of service endpoint with service connection, added more verbosity to the service connection parameters section to make it more clear which parameters need to be filled out.

Motivation

I tried to follow the instructions in order to create a new service connection for OIDC and found the instructions difficult to understand. In some situations, they were inaccurate or the terminology was incorrect.

Related Issue(s), If Filed

N/A

Testing

N/A

Checklist

• I have read the README document
• I have read the CONTRIBUTING document
• My code follows the code style of this project
• I have added tests to cover my changes
• A short description of the change has been added to the changelog using the script npm run newChange

License

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

[hayemaxi]

Thanks for this contribution! We appreciate the effort to disambiguate the docs. The changes look good to me- however- they seem to imply that setup with Microsoft Entra ID is required. I have found that I can use OIDC without this step. (example article https://aws.amazon.com/blogs/modernizing-with-aws/how-to-federate-into-aws-from-azure-devops-using-openid-connect/)

What does this step achieve? AFAIK this only entertains accessing azure services with OIDC from the pipeline (which are usually unnecessary for AWS based tasks), but I am not confident about this.