Crossfeed Registration and Approval Process

[nickviola]

🗣 Description

💭 Motivation and context

🧪 Testing

✅ Pre-approval checklist

• [ ] This PR has an informative and human-readable title.
• [ ] Changes are limited to a single goal - eschew scope creep!
• [ ] All future TODOs are captured in issues, which are referenced in code comments.
• [ ] All relevant type-of-change labels have been added.
• [ ] I have read the CONTRIBUTING document.
• [ ] These code changes follow cisagov code standards.
• [ ] All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
• [ ] Tests have been added and/or modified to cover the changes in this PR.
• [ ] All new and existing tests pass.

✅ Pre-merge checklist

• [ ] Revert dependencies to default branches.
• [ ] Finalize version.

✅ Post-merge checklist

• [ ] Create a release.

[nickviola]

We are aware of the vulnerability issues, can someone please confirm that these are known issues that will be addressed in a seperate PR?

[schmelz21]

We are aware of the vulnerability issues, can someone please confirm that these are known issues that will be addressed in a seperate PR?

@aloftus23 or @DJensen94 - I think we are okay with the Vulns, but can either of you give a approve or thumbs up to confirm. We'll then merge to master.

[schmelz21]

We are aware of the vulnerability issues, can someone please confirm that these are known issues that will be addressed in a seperate PR?

@aloftus23 or @DJensen94 - I think we are okay with the Vulns, but can either of you give a approve or thumbs up to confirm. We'll then merge to master.>

---

Actually, we can demonstrate that all Vulnerabilities are known via these PRs and Issues. @nickviola , Please go ahead and merge.

Address scrapy Vulnerability flagged by Github Actions Bump axios from 0.27.2 to 1.6.2 in /backend Bump axios and aws-amplify in /frontend Bump node from 18-alpine3.17 to 21-alpine3.17