Transaction call object to accept both input and data field if equal

[friedemannf]

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Most advanced CI tests are deferred until PR approval, but you could:

• locally run all unit tests via: ./gradlew build
• locally run all acceptance tests via: ./gradlew acceptanceTest
• locally run all integration tests via: ./gradlew integrationTest
• locally run all reference tests via: ./gradlew ethereum:referenceTests:referenceTests

PR description

#6094 introduced the option to provide the calldata via the input field instead of the deprecated data field. It also introduced a check that prevents both field from being set. This seems overly strict as it prevents clients from setting both fields to remain backward-compatible. This PR relaxes the check to only fail if both fields are set and they are not equal.

Fixed Issue(s)

fixes #6697

[friedemannf]

We might want to adjust the documentation here to specify this behavior:
https://besu.hyperledger.org/public-networks/reference/api/objects#transaction-call-object

[macfarla]

LGTM. test cases make it clear. Thanks for your contribution @friedemannf

[macfarla]

We might want to adjust the documentation here to specify this behavior: https://besu.hyperledger.org/public-networks/reference/api/objects#transaction-call-object

Thanks for this - added doc-change-required label for that purpose.