[BCI-2564] - TXM feature to drop stale unstarted transactions

[Farber98]

Description

Through this PR we are adding a new flow within /v2/keys/evm/chain WEB API endpoint to be able to drop 'unstarted' txes that are considered stale. New functionality will be exposed in the node operator UI (see UI changes).

How it works

When we mark abandonUnstarted = true, we can optionally pass a subject

• If no subject is provided, ALL 'unstarted' txes will be DELETED.
• If a subject is provided, we only delete THOSE SUBJECT 'unstarted' txes.

Acceptance Criteria

• Be able to delete 'unstarted' stale txes from a button within Node Operator UI.

Tickets:

• BCI-2564
• BCI-2563: The UI one.

Unblocks:

• Add button to drop 'unstarted' txs operator-ui#80. Useful context within PR description.

Mitigates:

• INCIDENT-713

[Farber98]

subject should be optional or mandatory?

Note: I'm assuming subject is a way to classify certain operations, but not sure what exactly we are classifying. Same product txes? Same NOP process txes?

[Farber98]

If subject is optional and defaults to empty, is desired to delete all 'unstarted' txes when this occurs?

[Farber98]

Do we want to be able to abandon and abandonUnstarted on the same query? Are there any risk of some collision doing this? Should we limit that only one can occur in the same query?

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube

[Farber98]

Dropped in favour of https://smartcontract-it.atlassian.net/browse/BCI-3901