Release manifest-icons

[molant]

@sarvaje @hxlnt this hint is still not published "officially" although it seems we are using it seems to be active in different places. IIRC the missing piece was to update the documentation. Ideally we should do the badge/monochrome before we "release" it.

w3c/manifest#833 (comment)

Confirmed that Chrome does not use purpose: badge anywhere, including on the server-side infrastructure. From our perspective, we are good to rename it and change its semantics. LGTM.

@amazingcaio, thanks for catching this change!

Originally posted by @molant in #3841

[molant]

There are 2 PWA hints that are not published: #2351

This one is to track manifest-icons exclusively.

• Once Fix: Icon purpose doesn't support combination of values #3841 is done, badge
• Update docs and also point to the w3c manifest above in the section about issues

[antross]

This will entail removing private: true from the package.json and adding this hint to each of our default configurations (for the CLI, online scanner, browser extension, etc).

[hxlnt]

This is blocked on #2351; I will take a look next sprint. Once the docs are updated, @sarvaje will update the package.json.

[Seirdy]

Would be great if it could also check if the manifest icons are cache-busted.