macOS setup experience: "Spiffier" improvements

[noahtalerman]

• @noahtalerman: Noticed these things when I setup my new Mac:

1. Strange/inconsistent border/button styles for EULA: https://drive.google.com/file/d/1c3Z_s_TkghhvD0eftPA5mpbBrrtPLB0P/edit
2. Strange/inconsistent styles for setup experience “splash screen” that shows before setup experience software:

3. Let's set time/action expectations with end users during setup experience software page (picture above). Something like "You have to wait 20 minutes and you don’t have to do anything." "You can step away." Also remove "Install" and rename "Process" to something less technical like "Item"
4. Also, let's give end users a way to access hardware info like serial number if they can't already via Apple menu. That way, end users can share this info w/ IT admins when troubleshooting errors.

Goal

User story
As an end user setting up my new Mac,
I want to see a clear, consistent setup experience
so that I have a strong first impressions of the Fleet brand.

Changes

Product

• UI changes: TODO
• CLI (fleetctl) usage changes: TODO
• YAML changes: TODO
• REST API changes: TODO
• Fleet's agent (fleetd) changes: TODO
• Fleet server configuration changes: TODO
• Exposed, public API endpoint changes: TODO
• fleetdm.com changes: TODO
• GitOps mode UI changes: TODO
• GitOps generation changes: TODO
• Activity changes: TODO
• Permissions changes: TODO
• Changes to paid features or tiers: TODO
• My device and fleetdm.com/better changes: TODO
• Usage statistics: TODO
• Other reference documentation changes: TODO
• 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: TODO
• Feature guide changes: TODO
• Database schema migrations: TODO
• Load testing: TODO
• Pre-QA load test: TODO
• Load testing/osquery-perf improvements: TODO
• This is a premium only feature: Yes / No

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

Risk assessment

• Requires testing in a hosted environment: TODO
• Requires load testing: TODO
• Risk level: Low / High TODO
• Risk description: TODO

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

• TODO

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":

[rderewianko]

Could I also request a consideration of "removing the close button" on the install software pane? it's just.. odd