Separate blocks for each registered operation

[jlashner]

Changes registry block structure so that each operation has its own block.

Description

It is possible for the operation list of an agent to change, if that agent is updated without restarting the registry. This will crash the registry and prevent it from publishing data since the block-structure of the feed depends on the available agents. This changes the registry so that each operation has its own block, allowing for the operation list to change without crashing the registry.

Motivation and Context

Solves issues where updating agents without restarting the registry causes it to crash.
Resolves #311.

How Has This Been Tested?

Ran registry tests locally.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[BrianJKoopman]

Sorry this took so long for me to test. I was wondering if there were any implications past the registry in the system of splitting up the blocks and wanted to AB test opening files with and w/o the patch. In doing so I did notice a bug in the field name assignment.

[BrianJKoopman]

Thanks for the update. Tested one more time, things look good to me now!