feat(server)!: the endpoint complete campaigns is switched to the post method

[AndrusGerman]

Reason

Solve problem 3117 which is to change the endpoint from GET to POST of the route that completes the campaign

Changes

• controllers/api/campaign.go: Changed the enpoint method from POST to GET in campaigns/{id:[0-9]+}/complete

• static/js/src/app/gophish.js: Changed the enpoint method from POST to GET in query("/campaigns/" + id + "/complete", "POST", {}, true)

• Compiled the corresponding JavaScript with Gulp (static/js/dist/app/autocomplete.min.js, static/js/dist/app/campaign_results.min.js, static/js/dist/app/settings.min.js...)

[jordan-wright]

For backwards compatibility, I think we should support GET and POST in the server-side handler, then change the frontend to use POST (like you have here).

Then, the release notes for an upcoming release we could say that the GET endpoint is deprecated and will be removed in the following release. That way, folks that use the API will have a release to update their code.

Also, if you could please remove the minified JS files, it'd be appreciated! We'll build those ourselves since they're tough to review.

[AndrusGerman]

I will be making the corresponding changes 🫡

[AndrusGerman]

For backwards compatibility, I think we should support and in the server-side handler, then change the frontend to use (like you have here).GET``POST``POST

Then, the release notes for an upcoming release we could say that the endpoint is deprecated and will be removed in the following release. That way, folks that use the API will have a release to update their code.GET

Also, if you could please remove the minified JS files, it'd be appreciated! We'll build those ourselves since they're tough to review.

This should be enough 😊 @jordan-wright