Binary Serialization Standard

[ACStone-MTS]

What does this PR fix/introduce?

This PR turns the "Serialization Standard" into the "Binary Serialization Standard" and splits it into multiple pages for ease of reading.

The document itself now includes all updated Condor types outside of the chainspec, which will be a separate PR.

Closes #1471 #1378

Additional context

// Add further detail on the current situation, or what the PR seeks to address.
// Include loom, screenshots, or gifs(record, compress) if helpful.

Checklist

(Delete any that aren't relevant)

• Docs are successfully building - yarn install && yarn run build.
• For new internal links I used relative file paths (with .md extension) - e.g. ../../faq/faq-general.md - instead of introducing absolute file path, or relative/absolute URL.
• All external links have been verified with yarn run check:externals.
• My changes follow the Casper docs style guidelines.
• All technical procedures have been tested (if you want help with this, mention it in Reviewers).
• If structural changes are introduced (not just content changes), cross-broswer testing has been completed.

Reviewers

TBD

[ACStone-MTS]

@bradjohnl I'm getting a strange failure on the CICD for this one - could you take a look when you get a chance?

[bradjohnl]

@bradjohnl I'm getting a strange failure on the CICD for this one - could you take a look when you get a chance?

Hey @ACStoneCL . It's fixed. I've removed some hardcoded, and apparently redundant tests that were targeting pages that this PR removed / changed.

I've created an internal issue in our SRE board to check the testing strategy and make sure we are already testing each internal and external link with other processes (namely the: node check-external-urls.js test script).

[ipopescu]

I left a few minor nits and a few questions about some methods I don't see anymore. It would be good to address these before approving.

While reviewing this file, a few other questions came up:

• There's a bit of duplication with the json-rpc/types_chain.md file, although the serialization section is much more detailed. Perhaps we can auto-generate the json-rpc docs in the future to avoid double maintenance.
• I see that some types are missing from what we expose in the JSON RPC; perhaps this is because they are not exposed in the RPC methods. Do you know why this the case?
  • Some of the fields I noted were: Message, MessageAddr, MessageLimits, MessagePayload, MessageTopicOperation, DeployConfig, TransactionConfig, TransactionHeader, TransactionId, TransactionWithExecutionInfo, BalanceHoldAddr, BidAddr, BlockGlobalAddr, BlockSignatures.

[ipopescu]

I tried to help resolve a conflict, and then I had to fix a link for the build to pass.

[darthsiroftardis]

Approval pending comments from @ipopescu