Update edit page to account for type parameter

What does this MR do?

Update edit page to account for type parameter Alexander Turinske authored 2 hours ago

• update the policy editor to conditionally show components based on policy type passed in
• update tests

How to setup and validate locally (strongly suggested)

1. Follow the Protect Onboarding task to be able to create network policies in kubernetes/cilium
2. Follow the scan execution creation snippet to create some scan execution policies
3. Turn on the :security_policies_orchestration_configuration feature flag
4. Navigate to Security & Compliance => Policies
5. Change the security policy project

Screenshots or Screencasts (strongly suggested)

Page	Before	After
Policies#new		No visual change. Everything works as expected
Policies#edit, container_policy		(with !68317 (merged), but this is not dependent on it because this is all behind a feature flag anyways)
Policies#edit, scan_execution_policy		(with !68317 (merged), but this is not dependent on it because this is all behind a feature flag anyways)
ThreatMonitoring#new		No visual change. Everything works as expected
ThreatMonitoring#edit, container_policy		No visual change. Everything works as expected

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #338754 (closed) Related to #321884 (closed)