googlechrome: Remove persist User Data

[b4imetu]

Closes #XXXX

Relates to #7573 (comment)

• I have read the Contributing Guide.

In my humble opinion, it is unnecessary to save User Data in persist.

Same for Google Chrome - the non portable manifest crashes the browser (linked issue).

• There is no such problem for Google Chrome.
• It will cause two Chrome icons with different profiles to appear in the taskbar.
• The default browser opening method will also open a new profile.

troublesome for ordinary users.

[github-actions]

All changes look good.

Wait for review from human collaborators.

googlechrome

• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

[b4imetu]

for versions/googlechrome-beta
versions/googlechrome-canary
versions/googlechrome-dev
they do not persist User Data and they work well.

[github-actions]

All changes look good.

Wait for review from human collaborators.

googlechrome

• Description
• License
• Hashes
• Checkver
• Autoupdate
• Autoupdate Hash Extraction

[b4imetu]

please review this ty @aliesbelik @sitiom @rashil2000

[chawyehsu]

There wasn't any message left for this breaking change. The missing of my chrome profile confused me after the update.

At least the old persisted profile data should be copied to AppData and there should be a message notifying the change.

[chawyehsu]

Also, this made the persisted profile data being isolated and requires a manual deletion.

[rasa]

@chawyehsu Sorry 'bout that. I didn't realize this would break existing installs, or I would have never accepted it as is. I'll be more careful next time.

In my feeble defense, the PR was several months ago, and no one voiced a concern. Perhaps in these kinds of PRs, we should require at least 2, or even 3, approvals before merging.