Update docs for getting token for origin trial

[mikehoffms]

Rendered article sections for review (ordered per Files Changed page & doc build report):

1. What's New in Microsoft Edge DevTools
   • Type of change: Added caveat: What's New outdated.
   • Internal rendered: https://review.learn.microsoft.com/microsoft-edge/devtools-guide-chromium/whats-new/whats-new?branch=pr-en-us-2885
   • Public rendered: https://github.com/MicrosoftDocs/edge-developer/blob/user/mikehoffms/ot-link/microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
   • Before: https://learn.microsoft.com/microsoft-edge/devtools-guide-chromium/whats-new/whats-new
2. Test and automation > Use Origin Trials in Microsoft Edge
   • Type of change: Main. Removed dup/outdated content, pointed to green page instead.
   • Internal rendered: https://review.learn.microsoft.com/microsoft-edge/origin-trials/index?branch=pr-en-us-2885
   • Public rendered: https://github.com/MicrosoftDocs/edge-developer/blob/user/mikehoffms/ot-link/microsoft-edge/origin-trials/index.md
   • Before: https://learn.microsoft.com/microsoft-edge/origin-trials
3. Handle links to your Progressive Web Apps
   • Type of change: Added hidden comment that link handling != url handling.
   • Internal rendered: https://review.learn.microsoft.com/microsoft-edge/progressive-web-apps-chromium/how-to/handle-urls?branch=pr-en-us-2885
   • Public rendered: https://github.com/MicrosoftDocs/edge-developer/blob/user/mikehoffms/ot-link/microsoft-edge/progressive-web-apps-chromium/how-to/handle-urls.md
   • Before: https://learn.microsoft.com/microsoft-edge/progressive-web-apps-chromium/how-to/handle-urls
4. PWA > Experimental features and origin trials
   • Type of change: Updated link; instead of Console, green page. Added "See also" links.
   • Internal rendered: https://review.learn.microsoft.com/microsoft-edge/progressive-web-apps-chromium/how-to/origin-trials?branch=pr-en-us-2885
   • Public rendered: https://github.com/MicrosoftDocs/edge-developer/blob/user/mikehoffms/ot-link/microsoft-edge/progressive-web-apps-chromium/how-to/origin-trials.md
   • Before: https://learn.microsoft.com/microsoft-edge/progressive-web-apps-chromium/how-to/origin-trials
5. What's New in Progressive Web Apps
   • Type of change: Added caveat: What's New outdated. Updated link text 3x. Noted no longer origin trial 3x. Added See Also links.
   • Internal rendered: https://review.learn.microsoft.com/microsoft-edge/progressive-web-apps-chromium/whats-new/pwa?branch=pr-en-us-2885
   • Public rendered: https://github.com/MicrosoftDocs/edge-developer/blob/user/mikehoffms/ot-link/microsoft-edge/progressive-web-apps-chromium/whats-new/pwa.md
   • Before: https://learn.microsoft.com/microsoft-edge/progressive-web-apps-chromium/whats-new/pwa
6. Test and automation in Microsoft Edge
   • Type of change: Updated link; instead of Console, green page.
   • Internal rendered: https://review.learn.microsoft.com/microsoft-edge/test-and-automation/test-and-automation?branch=pr-en-us-2885
   • Public rendered: https://github.com/MicrosoftDocs/edge-developer/blob/user/mikehoffms/ot-link/microsoft-edge/test-and-automation/test-and-automation.md
   • Before: https://learn.microsoft.com/microsoft-edge/test-and-automation/test-and-automation
7. toc.yml table of contents file
   • Type of change: Added index entries for top-of-page title of all 10 PWA articles that have shortened TOC entries.
   • Internal rendered: https://review.learn.microsoft.com/microsoft-edge/progressive-web-apps-chromium/how-to/?branch=pr-en-us-2885
   • Public rendered: https://github.com/MicrosoftDocs/edge-developer/blob/user/mikehoffms/ot-link/microsoft-edge/progressive-web-apps-chromium/how-to/index.md
   • Before: https://learn.microsoft.com/microsoft-edge/progressive-web-apps-chromium/how-to/

This PR fixes Issue MicrosoftEdge/MSEdgeExplainers#702 -
[Origin Trial] How to sign in to developer console to enroll for origin trial?

AB#47170262

[captainbrosset]

I left two suggestions, and shared my point of view on the 3 outdated origin trials.

I could leave with both options for What's New (either always correct, or snapshot in time), but I tend to lean towards the snapshot in time side. I like the fact that these pages can serve as historical proofs that some things happened. It's also less work for us.

[captainbrosset]

Just to close the loop on this, I think the accepted solution is:

1. Add a note at the top of our various What's New pages that say something like: "Sections of this document correspond to historical releases of Microsoft Edge and are not updated over time. References to new features and experiments might become outdated as new versions of Microsoft Edge get released.".
2. For PWA specifically, maybe change it to: "...References to new features and origin trials might become outdated..."
3. As a best effort, add notes next to individual PWA what's new entries that mention the state of the origin trials. Something like: "This origin trial has ended and the feature is now available". Or "This origin trial has ended and experimental support for this feature was removed".

cc @mikehoffms

[mikehoffms]

Just to close the loop on this, I think the accepted solution is:

1. Add a note at the top of our various What's New pages that say something like: "Sections of this document correspond to historical releases of Microsoft Edge and are not updated over time. References to new features and experiments might become outdated as new versions of Microsoft Edge get released.".
2. For PWA specifically, maybe change it to: "...References to new features and origin trials might become outdated..."
3. As a best effort, add notes next to individual PWA what's new entries that mention the state of the origin trials. Something like: "This origin trial has ended and the feature is now available". Or "This origin trial has ended and experimental support for this feature was removed".

cc @mikehoffms

done: 1, 2, and most of 3. so far, I haven't added quite so specific as:
"This origin trial has ended and experimental support for this feature was removed."
ready for your review @captainbrosset

eg added to DevTools What's New nav page:

What's New articles correspond to historical releases of Microsoft Edge, and are not updated over time.
References to "new features" and "experiments" might become outdated as new versions of Microsoft Edge are released.

[captainbrosset]

Looks good to me. I made three suggestions in the what's new PWA article to clarify whether the features that once were in OT are now available or not. Feel free to consider these suggestions and rephrase them if needed.

[amandabaker]

LGTM

[learn-build-service-prod]

Learn Build status updates of commit 53552ce:

✅ Validation status: passed

File	Status	Preview URL	Details
microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md	✅Succeeded	View
microsoft-edge/origin-trials/index.md	✅Succeeded	View
microsoft-edge/progressive-web-apps-chromium/how-to/handle-urls.md	✅Succeeded	View
microsoft-edge/progressive-web-apps-chromium/how-to/origin-trials.md	✅Succeeded	View
microsoft-edge/progressive-web-apps-chromium/whats-new/pwa.md	✅Succeeded	View
microsoft-edge/test-and-automation/test-and-automation.md	✅Succeeded	View
microsoft-edge/toc.yml	✅Succeeded	View

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel