refactor(platform)!: document creation/update/deletion does not refetch contract

[QuantumExplorer]

Issue being fixed or feature implemented

Document creation, update and deletion all told drive about the contract by setting the contract id. Drive would then refetch the contract from disk.

Even though most of the time it would fetch it from cache, this still was not ideal, because the processing cost of a fetch from cache is the same as a fetch from disk.

What was done?

A new type was created that encapsulates all types on data contract info, and we made the document operations in drive more straightforward hiding away most of the complexity. Now there are just a single operation allowed for adding, updating, or deleting.

How Has This Been Tested?

Tests continue to pass.

Breaking Changes

Since we no longer fetch the contract in drive, drive will report less processing costs, this means that this is a breaking change.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[PastaPastaPasta]

light utACK; generally seems to be a fine and correct refactor; there are a few things I wish were done in other PRs to make this more trivial to review. I find it is unlikely there are issues introduced here that wouldn't be caught by tests.

See comments