Add due diligence check

### Background

Create a check in the preHandle workflow that creates a due diligence error if a transaction does not follow the new normalized format.

### Acceptance Criteria

1. A transaction that uses `bodyBytes` to store the `TransactionBody` fails with a due diligence error.
2. A transaction that uses `signedTransactionBytes` also fails with a due diligence error.

### Dependencies

1. Prerequisite: #17448
2. Prerequisite: #17452

### Definition of Ready (DoR) Checklist

- [ ] Clear acceptance criteria
- [ ] Clear and detailed description
- [ ] Dependencies identified
- [ ] Links to documentation
- [ ] Should be completable in 2-3 Days
- [ ] Initial draft of Low-level design document
- [ ] At least high level test plan
- [ ] Groomed/Estimated

### Definition of Done (DoD) Checklist

- [ ] Acceptance Criteria complete
- [ ] No Codacy issues greater than minor (in new code)
- [ ] JavaDocs updated/created
- [ ] Code commented
- [ ] Unit tests created/updated
- [ ] 80% test code coverage (in new code)
- [ ] Happy Path and major negative cases in HAPI tests as applicable

Review the preHandle workflow and prerequisites #17448 and #17452 first; the issue does not name files or entry points beyond that workflow. Done means transactions using bodyBytes or signedTransactionBytes produce a due diligence error, with unit tests and applicable HAPI tests updated.

Written by the indexing model from the issue text.