fix(hermes): Eliminate almost all Debug print statements.

[stevenj]

Description

In line with the move to try and remove Debug prints from anywhere but Unit Tests, and Debug builds, this PR removes
all but the Debug print lints from the wasm bindings.

There is currently an issue in clippy which prevents the clippy lint for these issues being silenced in a macro like bindgen! which
is why they have not silenced. There are also no bindgen! options to not emit Debug implementations of automatically created types.

During this process there were a couple of minor changes which helped the process.

1. Any Specificially types Error, which was not used as a Specifically typed error, was changed to anyhow! this reduces the maintenance burden created by Typed errors, where no logic ever turns on the Error type itself.
2. Mutex<Arc<HashMap<>>> in the http connection manager was converted to a Dashmap. This made dealing with that type both more ergonomic, and also elimated a handful of error cases, which no longer needed errors thrown for the,
3. All unit tests were made so they will ONLY be able to run in debug builds.
4. Only Structs that are required to have Debug implemented to satisfy assert_* macros have been derived, and only in debug builds.
5. All Debug formatting has been eliminated.
6. Anyhow errors are serialized to error! logs using ToString which is equivalent to Display and just extracts the string in the anyhow! error, which is controlled and can not leak unexpected data. (Another reason to use Anyhow).
7. Silences lints on all todo! because this is not production code. But this will need to be reverted before we are production ready.

Related Issue(s)

No Specific Issue Yet

Breaking Changes

None, everything that was changed should be transparent.

Related Pull Requests

This was tested and built against this PR: input-output-hk/catalyst-ci#423
But that version is not used in this PR, because it is not yet ready to be merged, pending further testing.
Once merged, all these changes will eliminate a huge source of errors it will cause otherwise.

Please confirm the following checks

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream module

[cong-or]

looks good, I would agree with the comments from Rafal if you get a chance.