VIRTS-3996 Add everything adversary

[sgianvecchio]

Description

This change adds a new "everything" adversary with all adversary abilities. The everything adversary is automatically created during startup and updated whenever abilities are created or deleted via the UI.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• Launched Caldera and confirmed all adversary abilities show up under everything adversary
• Ran operations with atomic and batch planners, confirmed both work as expected
• Ran operations on Windows, Linux and Mac hosts

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code

[github-actions]

Wohoo! Your first PR -- thanks for contributing!

[mkultraWasHere]

@sgianvecchio super clean. I still need to test locally.

[CDJellen]

I'll echo @elegantmoose 's comments, the code is clean and parsimonious.

In performing some local testing, I've noticed a few behaviors which may be worth verifying and documenting.
The "Everything Bagel" Adversary:

• Abilities under the adversary object appear to be grouped first by their source plugin (e.g. access or stockpile) and then by their tactic (e.g. discovery or multiple).
• The order of the constituent abilities (and thus the atomic_order) appears to depend on the order in which abilities are located by the data_svc. As an example, abilities from the pathfinder plugin may appear above or below abilities from the access plugin between different sessions if the --fresh flag is applied on server startup.
• New abilities created through the UI or API are appended to the end of the "Everything Bagel" adversary as soon as they are saved with the data_svc.

Additional Thoughts:
This PR will fulfill the stated requirements of the "Everything Bagel" adversary. Adding these new methods directly to the data_svc has benefits in ensuring new abilities are registered and all abilities from across all plugins are included (these results may be harder to achieve if this were implemented in a plugin).

If, in the future, it is determined that there is a better place for these changes to live, we can discuss options. For now, the PR looks great to me, and I have identified no issues or edge cases in testing.

Thank you for this excellent first PR @sgianvecchio !

[sonarqubecloud]

Please retry analysis of this Pull-Request directly on SonarCloud.

[github-actions]

This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 5 days

[github-actions]

This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 5 days

[sonarqubecloud]

Please retry analysis of this Pull-Request directly on SonarCloud.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

90.0% Coverage
0.0% Duplication