Host details > OS settings: move OS settings table to dedicated Controls tab

[tux234]

Goal

User story
As an IT admin,
I want a better way to view OS settings (i.e. responses of many URI paths)
so that I can quickly and clearly understand where the problems are.

Changes

Product

• UI changes:
  • Figma wireframe.

• CLI (fleetctl) usage changes: No changes
• YAML changes: No changes
• REST API changes: No changes
• Fleet's agent (fleetd) changes: No changes
• Fleet server configuration changes: No changes
• Exposed, public API endpoint changes: No changes
• fleetdm.com changes: No changes
• GitOps mode UI changes: No changes
• GitOps generation changes: No changes
• Activity changes: No changes
• Permissions changes: No changes
• Changes to paid features or tiers: No changes—OS settings is Fleet Free
• My device and fleetdm.com/better changes: No changes
• Usage statistics: No changes
• Other reference documentation changes: No changes
• First draft of test plan added
• Once shipped, requester has been notified
• Once shipped, dogfooding issue has been filed

Engineering

• Test plan is finalized
• Contributor API changes: No changes
• Feature guide changes: TODO
• This is a premium only feature: No

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

Risk assessment

• Risk level: Low

Test plan

Make sure to go through the list and consider all events that might be related to this story, so we catch edge cases earlier.

Core flow

• From Host details > Controls hover and click on a row. Verify "Details" modal opens
  • Verify ability to copy details contents
  • Verify ability to scroll if contents goes beyond max-height
• Verify all states specified in the Figma on Apple, Windows and Android
• Verify "Resend" button functions as expected
• Verify Host Name template results show up on the controls list
• Verify Android Certificates show up in the controls list

Edge cases

• TODO

Supplemental testing

Testing notes

Confirmation

1. Engineer: Added comment to user story confirming successful completion of test plan (include any special setup, test data, or configuration used during development/testing if applicable).
2. QA: Added comment to user story confirming successful completion of test plan.
3. QA: Determined whether this story needs Playwright automation.
   • Needs automation: Yes / No
   • If yes, filed a follow-up issue in the :help-qa project with status "Needs automation":

[melpike]

Hey @tux234, could you share the Windows CSP profile you used for testing so I can reproduce?

[MagnusHJensen]

@tux234 @melpike Moving to g-power-to-pc since they own Windows now.