Add broker updater mechanism

[jotaemepereira]

Task

https://app.asana.com/0/1203581873609357/1205378118665592/f

Description

This adds the following changes:

When inserting/editing a profile

• When we insert a new profile, we get the list of brokers from the resources list and create the scan operations along with the profile queries.
• When we edit the profile, we do the same flow but fetch the brokers from the database

Before the scheduler starts running the operations
Here, we check for updates to the broker's list or new ones added. Because this operation could have an impact on performance (it has to go through the JSON files, decode them, and compare them to the database ones) it will run if it didn’t run in the last 24 hours (this constant can be changed)

Steps to test

Scenario 1 - User inserts a new profile

• Start from scratch (delete Vault.db)
• Create a new profile
• Check that scan operations are created for all the broker JSON files (fake ones should not be included)

Scenario 2 - User edits a profile

• Edit the profile
• Check that new scan operations are created with the new profile queries and the broker that is in the database (not in resources)

Scenario 3 - There are updates to a broker JSON file

• Have a profile, run some scans, and then stop the app
• Delete UserDefaults by running defaults com.duckduckgo.macos.browser.debug
• Grab one of the broker JSON files and increase the version number
• Run the app again, the broker JSON file should be updated in the database before running

Scenario 4 - There is a new JSON file

• Have a profile, run some scans and then stop the app
• Delete UserDefaults by running defaults com.duckduckgo.macos.browser.debug
• Create a new broker JSON file
• Run the app again, the broker JSON file should be updated in the database and the new scan operations should be added

[github-actions]

	Warnings
⚠️	PR has more than 500 lines of code changing. Consider splitting into smaller PRs if possible.

Generated by 🚫 dangerJS against 118d3a9

[Bunn]

Nice job, left some comments there, none are blockers, but the dependency injection ones are probably good ones to tackle now, but I'll leave it to you.
Nice job!