Customize conditional access policies

[rachaelshaw]

Goal

User story
As a As a Client Platform Engineer,
I want to choose which failing policies to use for conditional access automations
so that I can also use non-blocking policies.

Key result

Customer requests

Original requests

#24423

Context

• Product designer: @rachaelshaw

Follow-on to #19235

Changes

Product

• UI changes: TODO
• CLI (fleetctl) usage changes: TODO
• YAML changes: TODO
• REST API changes: TODO
• Fleet's agent (fleetd) changes: TODO
• GitOps mode changes: TODO
• Activity changes: TODO
• Permissions changes: TODO
• Changes to paid features or tiers: TODO
• Transparency changes: TODO
• First draft of test plan added
• Other reference documentation changes: TODO
• Once shipped, requester has been notified
• Once shipped, dogfooding issue has been filed

Engineering

• Test plan is finalized
• Feature guide changes: TODO
• Database schema migrations: TODO
• Load testing: TODO

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

• Requires load testing: TODO
• Risk level: Low / High TODO
• Risk description: TODO

Test plan

1. Step 1
2. Step 2
3. Step 3

Testing notes

Confirmation

1. Engineer: Added comment to user story confirming successful completion of test plan.
2. QA: Added comment to user story confirming successful completion of test plan.