Update main with master

[JamesSingleton]

Description

Update main with master

Motivation and Context

How Has This Been Tested?

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)
• Dependency update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• Performance tests should be ran against the server prior to merging.
• This change impacts caching for client browsers.
• This change impacts HTTP headers.
• This change adds additional environment variable requirements for One App users.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using One App?

[github-actions]

📊 Bundle Size Report

file name	size on disk	gzip
app.js	276.2KB	82.4KB
runtime.js	15KB	5.4KB
vendors.js	117.4KB	36.4KB
app~vendors.js	425.2KB	111KB
service-worker-client.js	17KB	5.2KB
legacy/app.js	291.4KB	85.6KB
legacy/runtime.js	15KB	5.4KB
legacy/vendors.js	172.9KB	47.1KB
legacy/app~vendors.js	439.9KB	114.1KB
legacy/service-worker-client.js	17.5KB	5.4KB

Generated by 🚫 dangerJS against dac22a7