[Frontend] Allow users to configure `skip_ci` behavior in scan execution and pipeline execution policies

Description

In Make [ci skip] configurable for pipeline execut... (&15647 - closed) (MR: !173480 (merged)) we are introducing backend / YAML mode for configuring ci.skip / skip_ci behaviors for pipeline execution policies.

!174191 (closed) addresses this in scan execution policies.

As a follow-on, we will want to explore the frontend changes required for this support.

Proposals

💡 Create an Advanced configuration section for any nuanced settings such as this

Allow for new rules / configurations to be added with a + - a few ideas:

  • + Add advanced configuration
  • + Add new rule
  • + Add new configuration rule

This would allow for scalability to apply new, varied rules that may be advanced, and scalable for any policy type.

Once selected, a list of available "advanced configuration rules" would appear. In this case, there would be one for now:

Configure exceptions for ci.skip`

Once this is selected, a new section for this rule appears.

We have a similar pattern for branch exceptions:

image

We may not need a checkbox in this case but a dropdown selector to pick from existing users or bots available in the project.

This could look like:

Configure exceptions for ci.skip

Block ci.skip except for the following users or bots: [ Select Users/Bots ]

Edited by Grant Hickman