add arbitrum error already known

[poopoothegorilla]

One of the RPCs on Arbitrum Sepolia returns 400 status code on TransactionAlreadyKnown error, that breaks our error classification and causes MultiNode to log critical error due to contradictions in results (one of the RPCs returns success and TransactionAlreadyKnown is classified as Unknown)

[github-actions]

I see you added a changeset file but it does not contain a tag. Please edit the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[prashantkumar1982]

Did we get an answer from Tenderly if this was indeed an intended change?
Last I heard, they acknowledged they may have mis-categorized this under 400 instead of 200.
If they agree and fix their side, do we still want to go ahead with this fix?