Fix Windows install branding constants

[Stephen Karl Larroque (lrq3000)]

Summary

• set BrowserOS company and safe browsing names in Windows install constants (fixes Installer overwrites existing Chromium installation instead of separate install #765)
• add a unit test to guard install identity constants

Testing

• python -m unittest discover -s packages/browseros/tests

PR generated with Copilot cloud agent using GPT-5.2-codex.

I could not test the fix myself because I could not compile, I don't have the required stack, but I reviewed the code change and the logic and the fix makes sense to me.

Please test beforehand to check if it works (if someone can make a build - maybe by triggering a gh action - I will gladly try !).

---

Summary by cubic

Update Windows install identity to use BrowserOS branding. Ensures install paths and Safe Browsing client name are correct and adds a test to prevent regressions.

• Bug Fixes
  • Set kCompanyPathName and kProductPathName to "BrowserOS" and kSafeBrowsingName to "browseros" in packages/browseros/chromium_patches/chrome/install_static/chromium_install_modes.h.
  • Added packages/browseros/tests/test_install_modes_patch.py to assert the constants and guard future changes.

^{Written for commit c03ccd4. Summary will update on new commits.}

This specific bug is Windows-only. The constants we changed live under chrome/install_static (Windows install path/registry identity). macOS/Linux installs use different mechanisms and aren’t affected by these Windows install identity values.

Agent-Logs-Url: https://github.com/lrq3000/BrowserOS/sessions/aca7c90e-815e-41b0-b423-616b591ae881

[greptile-apps]

PR author is not in the allowed authors list.

[github-actions]

Thank you for your contribution! Before we can merge this PR, we need you to sign our Contributor License Agreement.

To sign the CLA, please add a comment to this PR with the following text:

I have read the CLA Document and I hereby sign the CLA

You only need to sign once. After signing, this check will pass automatically.

---

Troubleshooting

• Already signed but still failing? Comment recheck to trigger a re-verification.
• Signed with a different email? Make sure your commit email matches your GitHub account email, or add your commit email to your GitHub account.

- - - I have read the CLA Document and I hereby sign the CLA - - - _{You can retrigger this bot by commenting **recheck** in this Pull Request. Posted by the **CLA Assistant Lite bot**.}

[Stephen Karl Larroque (lrq3000)]

I have read the CLA Document and I hereby sign the CLA

[Stephen Karl Larroque (lrq3000)]

I repeat: I have read the CLA Document and I hereby sign the CLA

[Stephen Karl Larroque (lrq3000)]

recheck

[Stephen Karl Larroque (lrq3000)]

I think the CLA bot is breaking here because it thinks the GitHub Copilot bot is a commit author that also needs to sign the CLA, which is not possible. This will require manual intervention by a human maintainer of BrowserOS.