Refactor Data Architecture for Equalify Schema

[bbertucc]

What problem is the feature trying to solve?

The existing data architecture drops data from scans (outlined in #262). The architecture also follows no set standard (see #257).

Desired Solution

To resolve those issues, I created https://github.com/equalifyEverything/equalify-schema

This issue includes work around integrating the STREAM schema.

Alternatives

Keeping our existing schema, we could update the way we handle tags and standards.

Technical Details

• [x] Incorporating STREAM means validating updating https://github.com/EqualifyEverything/scan.equalify.app so it returns results in STREAM format.
• [x] From there, we can update the DB install to be in line with Equalify Schema then update the scan process).
• [x] We'll also need to update the scan processor.
• [x] Equalify's API should also return data in Equalify Schema
• [ ] Finally, we can update the frontend so it works with Equalify Schema and the API (#298)

Equalify won't be handling conversion anymore once this issue is done.

All updates are tracked on the branch related to this issue.

[bbertucc]

Finishing this issue is currently blocked until we resolve https://github.com/EqualifyEverything/scan.equalify.app/issues/25 - in the meantime, I'll placeholder data.

[bbertucc]

We're almost done. Here is a video walkthrough of the new processor, ready for STREAM: https://youtu.be/_FhZIbHHar8

[bbertucc]

Discovery and Scanning feature not work with STREAM. Here is a video demo: https://youtu.be/prpkh-_OcU8?si=ntbhZYgK_RbPerG7

[bbertucc]

Added refactoring the API to this issue.

[bbertucc]

I'm going to close this and open an issue about the API, even though the frontend is not complete.