Part 2 of Workflow API swagger doc

[jdcmsd]

The second vast and trunkless leg of stone arrives to stand in the desert. All that remains is the attendant shattered visage, with sneer of cold command (telling that its sculptor well those passions read!).

...By this I mean, this is the lion's share of the Workflow API — nearly 100% complete. There are several endpoints marked with an "under construction" emoji for one of two reasons:

• Their data body is a multipart form, and I need to study up on exactly how those are structured, OR
• Some error prevents them from firing within the playground, such as the PATCH method, which succeeds on a curl call but throws a 406 Unacceptable Status in Swagger.

I figured these two exceptions are not enough reason to delay the other endpoints' doc from entering the product.

Proposed Changes

• Swagger annotations added to remaining WorkflowResource methods.
• Added four new wrapper classes to assist in schema/entity reflection.

Checklist

• Tests
• Translations
• Security Implications Contemplated (add notes if applicable)

This PR fixes: #29828

[dotcms-sonarqube]

Quality Gate passed

Issues
4 New issues
2 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[gavriella-dotcms]

The default value for actionId did not work on my playground on some of the endpoints, not sure if this is an issue from my end or not.

[jdcmsd]

Might warrant some research; I had thought that the System Workflow's actions' identifiers would be consistent across systems — i.e., it tests for me both on my local environment and on Demo.

If I'm wrong, though, I might need to pull some of those values and instead direct people to a method to procure the IDs.

But that can be the work of a different PR.