Support Scan on github tags

Is your feature request related to a problem? Please describe.
Currently, we use GitHub tags to manage microservice versions in our project. When I try to run a scan via workflow dispatch, I encounter the following error:

Describe the solution you'd like to see
I would like the ability to scan a specific GitHub tag to identify vulnerabilities in that version. It would also be beneficial to tag these versions as "production" or "development" (ideally with customizable tags to accommodate different versions in various regions).

Describe alternatives you've considered
Alternatively, we could create separate "production" and "development" branches, push changes to them, and use these branches exclusively for running Frogbot. However, this approach would add complexity, as each new deployment would require cherry-picking changes to each branch.

In my experience with other tools, specifying the version as an argument was a straightforward setup. This simplified the process and allowed us to easily identify issues in different development phases.

Start by tracing how workflow dispatch receives the repository ref and how Frogbot selects branches for scanning. Compare the requested GitHub tag input with the current branch-based flow, including production or development labels and regional customization. Done means a workflow can target a specific tag and identify its scan context without requiring separate branches.