v0.9.0 — share a project profile as a file

Added

• Export and import a project profile as a file. A developer prepares one profile — recipients, CC, subject prefix, Downloads subfolder, description template, project domains, recording limits — and sends the JSON to every tester, instead of each tester configuring Settings by hand and getting one field wrong.
• Importing shows what the file will add — the recipients above all — and stores nothing until it is confirmed. A profile file sets where finished reports are sent, so a file from an untrusted source could otherwise quietly redirect screenshots of a customer's application to a stranger.
• The exported file carries project settings only. Reporter details (name, customer number, AnyDesk) are per-person and never travel in a shared file, report history never leaves the machine, and the profile id is dropped so an import cannot overwrite an existing profile.
• Every field in an imported file is validated and clamped before it reaches storage: path escapes are stripped from the subfolder, recipients that are not addresses are dropped, domain patterns that would match every site are rejected, recording limits are bounded, over-long text is truncated, and unknown keys are discarded.

Changed

• The import confirmation button reads "Add and select this profile" rather than repeating the existing "Add profile" label, so no two controls in Settings say the same thing. E2E now also asserts that no two Settings labels collide.