Add a default way of serializing components

Currently, if we want to add a new component to Hypermine, boilerplate code has to be added to many different places in the codebase to allow data about this component to be transferred between the server and the client, along with additional boilerplate code to allow saving and loading.

When we start supporting a greater number of components, we should consider how to streamline the process of creating new ones, as this would make it less difficult for people less familiar with the codebase to add features.

One open design problem is how to serialize these components for saving, since naively relying on defaults would likely prevent save files from being compatible between versions of Hypermine.

As of June 2024, we probably need more components in place before we have enough information on how to perform such an abstraction.

No files, tests, or entry points are named in the issue. Begin by tracing how components are currently transferred between the server and client and how they are saved and loaded, then define a version-compatible default serialization approach. Done means reducing repeated component boilerplate without making save files incompatible across Hypermine versions.