Backfill Tests for Steve

[MbolotSuse]

Steve currently has limited tests. This creates a need for highly manual review of things like dependency bumps, and low confidence in the regression potential for changes. These tests should focus on how Steve would be used as a library and avoid mocking as much as is possible. Some potential examples:

• Adapting the test cases hosted in rancher to be ran directly in Steve's repo.
• Creating integration tests for the schemaDefinitions endpoint (which gives field definitions of each schema), including:
  • Add a CRD, make sure the definitions show up
  • Remove a CRD, make sure the definitions are no longer present
  • Try to access a schema that you can't see, make sure that neither the schema nor the definitions is present
  • Make sure a schema which uses openapi v3 specific fields has all fields correctly specified (example, provisioning.cattle.io.clusters)
  • Make sure a base schema which doesn't represent a k8s resource (e.x. generateKubeconfigOutput) has the fields properly specified
  • Make sure a resource that has multiple versions has the definition for the preferred group
• Tests for a custom action on a resource
• Tests for watch events on a resource
• Tests for creating/updating/deleting a resource
• Tests for watching a count