GH Action minutes consumption during waiting cycle

### Background

The Comparison mode in the AquaSec Scan Results repository is triggered on every commit. It is needed to make sure, that new commits do not bring new security alerts. But during busy hours, one triggered scan of developer branch on a bigger project can take up to 2 hours. That is huge waste of GH action minutes. This approach has to change, since it is expected to have this solution on tens of repositories.

### Goals

Find a way how to limit the GH Action minutes in an organization.

### Subtasks

- [x] #87

### Related / References

Options of solution:
- sleep the gh action for some time and revoke for few seconds to check the done state of the scanning flow
- run the solution instead of ubuntu-latest on the EC2s

Start by reading the repository's GitHub Action workflow that triggers Comparison mode on every commit, plus the completed subtask #87. The issue asks for a way to reduce Action minutes, with possible directions like polling instead of waiting or moving work to EC2. Done means there is an agreed design and implementation that lowers minutes across many repositories.

Escrita pelo modelo de indexação a partir do texto da issue.