chore: add secrets to actions that use the bot

[klmcadams]

Replace bot username and email with secrets and update corresponding examples

THIS IS A BREAKING CHANGE

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[klmcadams]

@SMoraisAnsys @germa89 @RobPasMue I applied your suggestions. The reason why I was using the environment variables was because of an article Jay shared with us a long time ago about secure development practices in GitHub actions. I haven't been able to find the article, but I'll share it with you if I find it

[klmcadams]

Here is an article that talks about using env variables to prevent script injection vulnerabilities: https://www.stepsecurity.io/blog/github-actions-security-best-practices#prevent-script-injection-vulnerabilities-2

Because of this, I think I should add back the env variable for at least the PR title

[RobPasMue]

Here is an article that talks about using env variables to prevent script injection vulnerabilities: https://www.stepsecurity.io/blog/github-actions-security-best-practices#prevent-script-injection-vulnerabilities-2

Because of this, I think I should add back the env variable for at least the PR title

Good find @klmcadams - let's do it only for the github-context related things.

[RobPasMue]

Or even all of them - as long as it is justified, that's fine by me

[klmcadams]

Ok! I'm going to follow this article - https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injections

[RobPasMue]

I have the feeling you missed some of them @klmcadams - sorry for going back and forth on all these inputs. At least now it's clear.