feat: add advanced retina performance test workflows

[ritwikranjan]

Description

This pull request includes changes to the GitHub Actions workflows to add a new advanced performance test and rename the existing performance test to basic performance test. The changes affect both the .github/workflows/images.yaml and .github/workflows/perf.yaml files.

The most important changes include:

Workflow updates:

• .github/workflows/images.yaml: Renamed the perf job to perf-basic and updated the test command to include -retina-mode=basic argument. [1] [2]

• .github/workflows/images.yaml: Added a new job perf-advanced for running the advanced performance tests with -retina-mode=advanced argument.

• .github/workflows/perf.yaml: Renamed the perf_test job to perf_test-basic and updated the test command to include -retina-mode=basic argument. [1] [2]

• .github/workflows/perf.yaml: Added a new job perf_test-advanced for running the advanced performance tests with -retina-mode=advanced argument.

Related Issue

If this pull request is related to any issue, please mention it here. Additionally, make sure that the issue is assigned to you before submitting this pull request.

Checklist

• I have read the contributing documentation.
• I signed and signed-off the commits (git commit -S -s ...). See this documentation on signing commits.
• I have correctly attributed the author(s) of the code.
• I have tested the changes locally.
• I have followed the project's style guidelines.
• I have updated the documentation, if necessary.
• I have added tests, if applicable.

Screenshots (if applicable) or Testing Completed

Please add any relevant screenshots or GIFs to showcase the changes made.

Additional Notes

Add any additional notes or context about the pull request here.

---

Please refer to the CONTRIBUTING.md file for more information on how to contribute to this project.

[timraymond]

I would use go-version, since go-version-file is only superficially functional. From the docs:

The go-version-file input accepts a path to a go.mod file or a go.work file that contains the version of Go to be used by a project.
The go directive in go.mod can specify a patch version or omit it altogether (e.g., go 1.22.0 or go 1.22).
If a patch version is specified, that specific patch version will be used.

Which is in direct conflict with the go.mod spec which states:

Syntax

go minimum-go-version

minimum-go-version
The minimum version of Go required to compile packages > in this module.

This is an open issue here: actions/setup-go#543

Plus, parameterizing go-version would allow us to use a matrix to do early testing for pre-release go versions to detect performance regressions.