Adding Draft Validate functionality into main

[tbarnes94]

Description

Host of new features to enable the draft validate command into the main branch.

Fixes # (issue)
Feature # (details)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Is it a breaking change which will impact consuming tool(s).

• Unit test suite for cmd/validate and pkg/safeguards

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[davidgamero]

note: rebased #279 here onto main to handle divergent branches from patching go module versions

[OliverMKing]

LGTM. Left a few comments but nothing blocking. Good work!

In the future it seems straightforward to make this support json and helm files too which would be great!

One concern I have is how the scheme is used. I can't find how it's used but if it's used for reading customer's manifests it could fail if they use a CRD. If it's just used for loading our policy definitions then there's no problem there

[davidgamero]

lgtm great work!