fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId

[petermetz]

In the DeployContractSolidityBytecodeNoKeychainV1Request of packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object).

Fixes #3586

Signed-off-by: Peter Somogyvari peter.somogyvari@accenture.com

Pull Request Requirements

• [x] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• [x] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• [x] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• [x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• [x] Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners For rebasing and squashing, here's a must read guide for beginners.

[petermetz]

I investigated why the DAST scan is failing but could not reproduce the problem locally. I'm going to assume that it's an issue with the environment setup logic of the CI job and not an issue with the endpoints. Based on that I'll disable the DAST scan for now until we can figure out what's wrong with it.

Tracking the fix here: https://github.com/hyperledger-cacti/cacti/issues/3596