Summary of Changes

Hello@lvoelz, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This PR refactors thecreate_note.go file to use attestations instead of vulnerabilities, aligning with an internal deprecation guideline. The change involves updating thegrafeaspb.Note type fromNote_Vulnerability toNote_Attestation and adjusting the note's content accordingly.

Highlights

• Intent: This pull request updatescreate_note.go to switch from using 'vulnerabilities' to 'attestations' when creating notes. This change aligns with the deprecation of third-party metadata as described ingo/aa-deprecate-3p-metadata.
• Changes: The primary change is incontainer_registry/container_analysis/create_note.go. ThecreateNote function'sgrafeaspb.Note type definition has been modified. Specifically, theType field now usesNote_Attestation instead ofNote_Vulnerability, and the associatedVulnerabilityNote structure has been replaced with anAttestationNote containing aHint with aHumanReadableName.
• Reviewer Activity: No reviewer activity has been recorded yet for this pull request.

Thanks for the updates!

It looks like there are some small consistency updates needed:

• This repo requires all commits to have messages that start a certain way. For this PR, each commit should start with something like:fix(‎container_registry):
  • updating the commit message for something already pushed to GitHub has a couple of fiddly steps, detail here:https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message#amending-older-or-multiple-commit-messages
• Lint failed... it looks like runninggo fmt ./... (reformat all files in this and subdir) incontainer_registry/container_analysis should fix it.