Improve CI Workflow with ESLint/Prettier Automation and PAT Usage

[cheesea3]

Summary

This PR enhances our Continuous Integration (CI) pipeline by automating code formatting with ESLint and Prettier more robustly. It also introduces the use of a Personal Access Token (PAT) to trigger subsequent workflow runs following automated commits.

Changes

• Automated Code Formatting: We now automatically run ESLint and Prettier on pull requests. If the code does not conform to our linting rules, it is automatically fixed and committed by the workflow.
• Conditional Workflow Execution: To prevent recursive workflow runs, we've implemented a conditional check that aborts the workflow if an automated commit is detected, thereby preventing potential infinite loops.
• PAT Integration: A PAT replaces the GITHUB_TOKEN for commits within the workflow. This change ensures that commits made by the workflow to the PR branch can trigger subsequent workflows, a feature not supported by the default GITHUB_TOKEN.

Benefits

• Improved Code Quality: Ensures all code submitted via PRs is automatically linted and formatted, maintaining consistency across our codebase.
• Streamlined Workflows: Developers can focus on their work without manual linting interventions, saving time and reducing the risk of human error.
• Enhanced Security and Compliance: By using a PAT with the necessary limited scopes, we can securely automate our workflow runs without compromising security.

Additional Notes

• The PAT is stored securely as a secret within our repository settings