bottlerocket apiserver tests

Create tests that interact with the apiserver on Bottlerocket and check that it does what is expected. Note, this is much deeper than it sounds since apiserver changes Bottlerocket settings. Consider for a moment that we might want to check kernel lockdown mode (for example) and see that kernel lockdown mode was in-fact enabled. We might even want to go further and reboot the system to make sure kernel lockdown mode is actually in effect.

The current issue represents the writing of some initial tests that perhaps are not so complex as requiring reboots. In any event, I suspect we want to model these as os tests (#426) in order to support complex requirements such as rebooting to check the setting-changes.

These almost certainly will require "exclusive access" for certain tests: #429

depends on:
- #426
- #429

Start by reading the os-test work in #426 and the exclusive-access requirements in #429, since this issue depends on both. Define initial tests that interact with the Bottlerocket apiserver without rebooting, and consider how setting changes such as kernel lockdown mode will be verified; done means those tests reliably confirm the expected changes.

Written by the indexing model from the issue text.