FCHashMap code readability and documentation improvement

[swirlds-automation]

I recently spent time reviewing PR: https://github.com/swirlds/swirlds-platform/pull/6447 Without diagrams and documentation it was very hard to read to make sense of.

Anybody who needs to understand that code would have a very hard time and either will have to reach out to the author or as most developers do just be brave and spend a lot of time reading it.

Based on personal experience

1. A few simple diagrams preferably embedded to the javadoc
2. Naming variables as close to the problem they solve, though this is always difficult to get it right
3. Add succinct (tricky) documentation at the right(tricky) places

[swirlds-automation]

This might be a good starting point: https://lucid.app/lucidchart/5b8f3bdd-47d5-481d-8460-7460e74a3a77/edit?viewport_loc=-1335%2C-243%2C4779%2C2583%2C0_0&invitationId=inv_ba5e7456-8519-47c3-a709-6e04e5401cdd _{author:cody-littley, createdAt:2023-01-18T14:54:04Z, updatedAt=2023-01-18T14:54:04Z}

[swirlds-automation]

Having good documentation for this class is important, even if we end up fully replacing all MerkleMaps with VirtualMaps. There are intended use cases for FCHashMap that won't involve MerkleMap. _{author:cody-littley, createdAt:2023-01-18T14:55:05Z, updatedAt=2023-01-18T14:55:05Z}

[swirlds-automation]

_{migrated from: url=https://github.com/swirlds/swirlds-platform/issues/6551 author:deepak-swirlds, #:6551, createdAt:2023-01-17T16:39:55Z, updatedAt=2023-02-17T22:55:39Z labels=Migration:Data}