Add validation checks to request-validator-access

[juan-malbeclabs]

Currently, the request-validator-access command does not perform the same pre-checks as prepare-validator-access. As a result, if any required argument or configuration is incorrect, the transaction is still sent on-chain and ends up being rejected.

We should:

1. Add the same validation logic from prepare-validator-access into request-validator-access, so that incorrect inputs stop execution before sending the transaction.
2. Introduce a new -f (force) flag that allows the transaction to be sent anyway. In this mode, the errors will be shown only as warnings, and the transaction will proceed regardless.

Benefits:

• Prevents unnecessary rejected transactions on-chain.
• Gives operators the flexibility to override checks when needed.

Acceptance Criteria:

• request-validator-access runs all the same validation checks as prepare-validator-access.
• Without -f, execution stops on validation errors.
• With -f, validation errors are downgraded to warnings, and the transaction is still submitted.

[vihu]

@juan-malbeclabs Is this still relevant?

[juan-malbeclabs]

Yes, the idea is that before making the request, it should validate that it’s feasible to approve it.

[karl-dz]

Addressed in #211