feat: Implement plugin system for archivists' parsers

[fkautz]

This commit introduces a flexible plugin system for archivists' parsers,
allowing new parsers to be registered dynamically. The system utilizes an
initialization function that registers parsers via a Register function. The
primary changes include:

• Creation of parser_registry.go to handle parser registration and storage.
• Modification of parserstorer.go to integrate the new parser registration
  system and utilize registered parsers during attestation storage.

This system enhances the extensibility of the parser functionality and improves
maintainability by decoupling the parser registration from the core logic.

Changes:

• Added internal/metadatastorage/attestationcollection/parser_registry.go for
  parser registration.
• Updated internal/metadatastorage/attestationcollection/parserstorer.go to
  support the new plugin system.

Signed-off-by: Frederick F. Kautz IV [email protected]

[fkautz]

For reference, this is the same pattern used by go-witness to add attestation types.

[codecov]

Codecov Report

Attention: Patch coverage is 41.66667% with 7 lines in your changes missing coverage. Please review.

Project coverage is 1.62%. Comparing base (a035c62) to head (96ea1a0).
Report is 96 commits behind head on main.

Files	Patch %	Lines
...adatastorage/attestationcollection/parserstorer.go	0.00%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #295       +/-   ##
==========================================
- Coverage   82.40%   1.62%   -80.78%     
==========================================
  Files          10     120      +110     
  Lines         358   28856    +28498     
==========================================
+ Hits          295     470      +175     
- Misses         43   28329    +28286     
- Partials       20      57       +37     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[fkautz]

I have two features coming up after this that depend on this patch:

• git attestations
• will refactor the omnitrail attestation for this

[jkjell]

Just a couple of questions centered around how to build out support for attestations outside of collections, as we keep generating more and more of those. 😅

[fkautz]

Just a couple of questions centered around how to build out support for attestations outside of collections, as we keep generating more and more of those. 😅

You know... we could refactor the whole code base to be plugin-based over time. (not serious but actually am?) 😅

I think there are several places where we can use a plugin system. We just need to make sure we can consistently trigger the correct plugin to avoid archivista getting confused.

Let me know if you think this would be a good idea. We can refactor this over time. I have two attestations to add after this patch. The subsequent patches will show off how an attestation parser would register and work. I was just waiting for @kairoaraujo's work to merge first because his most recent refactor patch changes what the details look like.