Fixed(CI): Fix PHP Compatability & PHP CodeSniffer workflow by using correct yaml syntax and `secrets` instead of `env`

[drikusroor]

Description

I've noticed that the PHP Compatability and the PHP CodeSniffer workflows have been consistently failing for the last weeks due to what appear to be a yaml syntax error:

A sequence was not expected
Unexpected type 'SequenceToken' encountered while reading 'job phpcs-compatibility'. The type 'MappingToken' was expected.

This PR then attempts to fix this yaml issue for both workflows and also uses the secrets key for better semantics.

Related GitHub issue(s)

n/a

Testing instructions

1. Go to the actions part of this PR and see if the workflows now succeed (or at least won't fail due to this yaml syntax error)

Screenshots / screencast

Changelog text for these changes

PR checklist

• [ ] I have tested my own code to confirm it works as I intended. I will be able to do this once the workflows have been approved by a maintainer :-)
• [x] My code follows the WordPress Coding Standards. n/a
• [x] My code follows the WordPress Inline Documentation Standards. n/a
• [x] My code includes automated tests for PHP and/or JS (if applicable). My code are the automated tests :D

[what-the-diff[bot]]

PR Summary

• Modifications to GitHub Workflow in php-compatibility.yml The manner in which GitHub workflow operates has been improved in this file, with a directory originally named env being replaced with a new one named secrets. This modification offers better data security by placing the token GH_BOT_TOKEN securely within the secrets structure.

• Improvements to GitHub Workflow in php-phpcs.yml A similar adjustment has been implemented in this file, the env directory has been replaced with a more secure one called secrets. As a benefit, the token REVIEWDOG_GITHUB_API_TOKEN is now securely located within the secrets block which increases security and reliability.