chore: backwards compat - open to team ideas!

[cmwylie19]

Description

Scaffolding for backwards compatibility. @defenseunicorns/pepr-dev let me know what you think, what else we want to include.

Related Issue

Fixes #312

Relates to #

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Unit, Journey, E2E Tests, docs, adr added or updated as needed
• Contributor Guide Steps followed

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.44%. Comparing base (5def05c) to head (7078078).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1707   +/-   ##
=======================================
  Coverage   79.44%   79.44%           
=======================================
  Files          48       48           
  Lines        2082     2082           
  Branches      428      428           
=======================================
  Hits         1654     1654           
  Misses        426      426           
  Partials        2        2           

[samayer12]

Good starting point on backwards compatibility. If this relates to us going to v1.0.0 eventually, maybe we should have @maryparsons, @daveworth, and @jeff-mccoy take a look to track team intent.

[samayer12]

Outstanding changes are left as open comments. Once resolved, we're good to merge.