Need a way to specify securityContext requirement in adapted resource manifest

[SteveL-MSFT]

Summary of the new feature / enhancement

Adapted resources currently don't have sections for operations as it's handled via the adapter. However, there should be a way to specify securityContext so that the check happens statically rather than failing at runtime

Proposed technical implementation details (optional)

Add get, set, test, delete (?), export sections to adapted resource manifest under a operations property that has a securityContext property. This allows for future extensibility.

[michaeltlombardi]

However we implement this, we should probably make sure to keep non-invocation options standardized across command manifests and adapted manifests, but operations.<operation>.<field> makes sense to me.