Closing/dismissing alerts

Today scan-action automatically creates new alerts in GH `Code Scanning Alerts` but as packages get auto fixed these alerts stick around.

1. Can `scan-action` look for alerts it "created" and close them when it can be determined they are fixed (i.e. package 1.2 has an error but the project now uses 1.3 - so dismiss the alert since it is stale/fixed)

According to this 3 years old issue https://github.com/anchore/scan-action/issues/142 then it's even worse, because dismissing these alerts will not help as `scan-action` will re-open them. I have yet to confirm this.

2. Can `scan-action` keep track of alerts it "created" but has been dismissed and not create new ones / reopen them as they should be considered muted ?

Maybe people have moved on to more useful code scanning tools that integrate better with GH? Any tips are welcome!

Start by reviewing how scan-action interacts with GitHub Code Scanning Alerts and verify the behavior described in issue 142, especially whether dismissed alerts are reopened. Done should mean defining and implementing reliable handling for alerts created by the action: closing those confirmed fixed and preserving dismissed alerts without recreating or reopening them.

Written by the indexing model from the issue text.