Feature - Manage payloads

[jbaptperez]

This is the GUI part of the payload management, which depends on the Caldera PR #2989.

• Adds a payload view:
  • Accessible from the navigation menu,
  • Handles payload file upload to data/payloads (and deletion),
  • Plugins payloads are excluded and left intact,
• Optional: Removes some white spaces in Navigation.vue,
• Optional: Excludes JavaScript generated files form the Docker context:
  • Lighten the Docker context when building a Caldera image, when some generated JavaScript files are present (local development),
  • Exclude such files as the Dockerfile handles itself the Vue.js file compilation.

[elegantmoose]

@jbaptperez reviewing and testing today. Apologies for delay.

[elegantmoose]

@jbaptperez How hard would it be also show all the payloads loaded in the Caldera, and then have just the local ones the user uploaded have the the ability to delete?

*might be useful to show all the payloads (and their source plugins) in the table as well. Or we should make it clear on the payloads view, that it is ignoring all loaded payloads from plugins.

[elegantmoose]

Tested on Mac. All functionality works as described.

[jbaptperez]

@jbaptperez How hard would it be also show all the payloads loaded in the Caldera, and then have just the local ones the user uploaded have the the ability to delete?

*might be useful to show all the payloads (and their source plugins) in the table as well. Or we should make it clear on the payloads view, that it is ignoring all loaded payloads from plugins.

@elegantmoose, I made the changes you asked for.

• I updated the payload view description to explicitly say that only local payloads can be uploaded or deleted (vs. plugin payloads),
• I split the table into 2 tables: Local editable payloads and plugin payloads (read-only). Only payloads of enabled plugins appear in the second table.

Technically, I had to use complete relative paths to payloads returned by the API (the GET new parameters I added in the previous caldera PR). Then, I processed the returned paths at the frontend side to properly extract the plugins name, whether the payload belongs or not to a plugin, etc. This kind of data process may be directly done at the backend side, but this would imply an API breaking change and (above all) a new PR on both caldera and magma repository: Too long.

[elegantmoose]

This LGTM, just that one new comment I left above, and then the move the payloads under the Configuration menu.

[jbaptperez]

This LGTM, just that one new comment I left above, and then the move the payloads under the Configuration menu.

@elegantmoose, done and rebased.

I also fixed the upload modal width (insufficient when using files with long names) and, as I just discovered there were another existing upload modal in the adversaries view, I adapted the payload one for consistency.

[elegantmoose]

@jbaptperez Thank you. 👏 Great PR.