Fix monitor API failures in kubernetes

[mgoelswirlds]

Description: This PR fixes the JavaScript REST API monitor that has a number of persistent failures when ran inside Kubernetes.

This PR modifies

• Add a route to REST JAVA APIs
• Add a route to Web3 APIs
• Add automatic default account for some endpoints resulting in /api/v1/accounts//
• /api/v1/status returns 409 even when there are failures
• Fix token_tests to check for non_empty list returned by tokens/{tokenId}/nfts which is further used to get serial_number

Related issue(s):

Fixes #8508 Fixes #8529

Notes for reviewer:

This has been tested on previewnet, testnet and mainnet.

Checklist

• [ ] Documented (Code comments, README, etc.)
• [ ] Tested (unit, integration, etc.)

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.41%. Comparing base (7ddf4a7) to head (194c38d). Report is 28 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #8583 +/- ## ============================================ - Coverage 92.41% 92.41% -0.01% - Complexity 7474 7475 +1 ============================================ Files 913 913 Lines 29788 29795 +7 Branches 3622 3627 +5 ============================================ + Hits 27529 27534 +5 - Misses 1440 1442 +2 Partials 819 819 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[mgoelswirlds]

Yes the 3 environments mentioned in the description do pass.