Feature: Display NOTICE.md in the About page

[hishitetsu]

Resolved / Related Issues
Items resolved / related issues by this PR.

• Related to Fix: Added notice for third party licenses #11483

Details
This may not be necessary since @d2dyno1 is working on the license page, but I submit it for reference.
NOTICE.md is included in the application package instead of referencing the online one since the third-party libraries used may change from version to version.
I also removed the link to the license of QuickLook since it is not included in Files and merely has the feature to call it.

Validation
How did you test these changes?

• Built and ran the app
• Tested the changes for accessibility

Screenshots

[0x5bfa]

FIiles don’t have display full license term. So if you’d like to add 3rd party notice in Files, display only package name by using Hyperlink Button as I told you what WinUI3-Gallery like. That’s sth kinda redundant.

[hishitetsu]

Displaying third party licenses is to comply with their licenses, so it is different from whether or not Files itself has the feature to display its own license.
For example, Windows Terminal does not have the feature to display its own license, but it does have third party notices.

(Sorry for Japanese)

[0x5bfa]

Me too Japanese, in fact. this PR's problem is redundancy.

[hishitetsu]

Me too Japanese, in fact.

I knew it! So I uploaded the screenshot in Japanese 😃

this PR's problem is redundancy.

That is a point to be discussed.
In Windows Terminal, the browser is opened to show the HTML file converted from NOTICE.md as third-party notices. I don't think this is a good idea, so I have embedded NOTICE.md in the About page.
In any case, users will not care much about third-party licenses, so I think it would be sufficient to display NOTICE.md as it is.

[yaira2]

@hishitetsu can you fix the merge conflicts?

[hishitetsu]

@hishitetsu can you fix the merge conflicts?

Successfully merged the upstream main.

[yaira2]

LGTM

[yaira2]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).