Update extension tutorial to use Manifest V3

[eclipse439]

As requested by multiple users, this PR updates docs to change manifest version to v3, as well as replace any deprecated functions.

I've also added a PR to update the source code linked in the docs here: MicrosoftEdge/MicrosoftEdge-Extensions-Demos#34

Issues requesting update: #2012 #1878

Rendered pages for review:
https://review.docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/getting-started/part1-simple-extension?branch=pr-en-us-2014
https://review.docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/getting-started/part2-content-scripts?branch=pr-en-us-2014

[captainbrosset]

Thank you so much for the PR @eclipse439! We'll give this a review soon.

[ashishnirvana1]

Iam fine by these changes, but am not fully sure if these cover everything. Will be nice to get a pass from Utkarsh Patankar as well.

[captainbrosset]

Iam fine by these changes, but am not fully sure if these cover everything. Will be nice to get a pass from Utkarsh Patankar as well.

Sounds great to me. @ashishnirvana1 are you able to at-mention them here? I don't know what their username is on GitHub.

[sonakshimore]

Iam fine by these changes, but am not fully sure if these cover everything. Will be nice to get a pass from Utkarsh Patankar as well.

Sounds great to me. @ashishnirvana1 are you able to at-mention them here? I don't know what their username is on GitHub.

@captainbrosset I am unable to add Utkarsh here as a Reviewer. Will get this reviewed offline and update this PR.

[Reezaali]

Still in review by @ashishnirvana1 to confirm that the tutorial is complete. We also need to implement tabs for MV2 and MV3.

@mikehoffms - can you update the doc with the tabs please?

[opbld30]

Docs Build status updates of commit fdc6c28:

✅ Validation status: passed

File	Status	Preview URL	Details
microsoft-edge/extensions-chromium/getting-started/part1-simple-extension.md	✅Succeeded	View
microsoft-edge/extensions-chromium/getting-started/part2-content-scripts.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[mikehoffms]

@Reezaali
I implemented tabs to preserve Manifest V2 code listings. The Files Changed tab served well, the sequence we used:

1. First, @eclipse439 had a chance to view the individual changed lines in the Files Changed tab.

2. Then, after I added tabs, the Files Changed tab no longer shows individual changed lines, but rather, confirms my correct restoration of V2 code listings: it shows that this PR adds a tab demarcator above the V2 listings (no other changes to V2 listings), and adds whole complete new V3 listings (not depicted as individual line changes).

[Reezaali]

For now, I will leave my review as blocking the merge until we hear back from @ashishnirvana1 to confirm that no additional changes are needed to the tutorial. Thanks!

[opbld31]

Docs Build status updates of commit b7fe1e3:

✅ Validation status: passed

File	Status	Preview URL	Details
microsoft-edge/extensions-chromium/getting-started/part1-simple-extension.md	✅Succeeded	View
microsoft-edge/extensions-chromium/getting-started/part2-content-scripts.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[sonakshimore]

Utkarsh has suggested the below changes to the documentation:

1. Change suggested to Create an extension tutorial, part 1 documentation, Step number 3 - last sentence:

Old version: Finally, ensure you register the pop-up in manifest.json under browser_action, as shown in the following code snippet.
New version: Finally, ensure you register the pop-up in manifest.json under browser_action or action in Manifest V2 or Manifest V3, respectively, as shown in the following code snippet.

2. Extension demos on Before you begin section of documentation:

Since it mentions that the source code has been updated from Manifest V2 to Manifest V3, we should actually update the source code first before we update this documentation.

Could you please review & approve GitHub PR #34 - Update Edge Extension Tutorials to use Manifest V3 by eclipse439 · MicrosoftEdge/MicrosoftEdge-Extensions-Demos?

[Reezaali]

@mikehoffms - I merged PR34 above as mentioned by @sonakshimore. Thanks.

[opbld31]

Docs Build status updates of commit ed86ec3:

✅ Validation status: passed

File	Status	Preview URL	Details
microsoft-edge/extensions-chromium/getting-started/part1-simple-extension.md	✅Succeeded	View
microsoft-edge/extensions-chromium/getting-started/part2-content-scripts.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[opbld32]

Docs Build status updates of commit dd549aa:

✅ Validation status: passed

File	Status	Preview URL	Details
microsoft-edge/extensions-chromium/getting-started/part1-simple-extension.md	✅Succeeded	View
microsoft-edge/extensions-chromium/getting-started/part2-content-scripts.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[mikehoffms]

This V2-specific word|sentence|paragraph needs techreview in future PR. chrome.extension.getURL is V2-specific. @ashishnirvana1 @eclipse439
rendered:
https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/getting-started/part2-content-scripts?tabs=v2
find chrome.extension.getURL then click tabs