Integrate Rollbar for error reporting

- [ ] Setup project
- [ ] Configure environments for testing in rollbar (dev, appveyor, production): https://docs.rollbar.com/docs/environments
- [ ] Configure code to always emit the proper environment
- [ ] Configure github: https://docs.rollbar.com/docs/source-control
- [ ] Configure and emit information about deployments: https://docs.rollbar.com/docs/deploy-tracking

- [ ] Basic unhandled error catching: https://docs.rollbar.com/docs/dotnet#section-winforms
- [ ] Log handled errors in Core, CLI, Winforms: https://docs.rollbar.com/docs/dotnet#section-code-level-error-handling
- [ ] Emit versions (git commit hashes) with errors/telemetry/logging: https://docs.rollbar.com/docs/versions
- [ ] Setup People Tracking to know how many users are affected by an issue: https://docs.rollbar.com/docs/person-tracking#section--net

- [ ] Disclosure & Consent for Users:
- [ ] Generally the Google Chrome and Play Store "Prominent Disclosure Requirement" seems easy to follow and sufficient: https://developer.chrome.com/webstore/program_policies
- [ ] Link to EULA in github (for use, separate from source license): https://termsfeed.com/eula/generator/
- [ ] Must have a privacy policy: Link to Privacy Policy in github and link to it from consent: https://termsfeed.com/privacy-policy/generator/
- [ ] Denote Rollbar as a partner & data processor: https://rollbar.com/compliance/gdpr/
- [ ] _disclose how the user data will be used_: Disclose that app collects and sends data for detecting and diagnosing errors and improving the application. We might show ads at some point, but we have no intention of selling any information that we collect to a third party.
- [ ] Consent: User must agree or the app shuts down. If the user doesn't want to agree, point them to source code and they can freely modify the program to suit their needs.

No files are named, so first locate the Core, CLI, and WinForms startup and error-handling entry points, plus any shared logging utilities. Check app configuration/build settings for environment and deployment metadata, then plan where Rollbar initialization should happen to emit handled/unhandled errors, versions, and telemetry. Finally, find the user launch/consent flow and add disclosure, privacy/EULA links, and opt-in shutdown behavior. Done means each runtime path reports as configured and consent controls error reporting exactly as described.

Escrita pelo modelo de indexação a partir do texto da issue.