FIREFLY-1925: Use MessagePack for Redis object storage.

[loitly]

Ticket: https://jira.ipac.caltech.edu/browse/FIREFLY-1925

This PR replaces Redis values currently stored as JSON strings and Java-serialized objects with MessagePack.

• New values are serialized using MessagePack.
• Reads remain backward compatible and can still handle existing Java-serialized and JSON values.

Motivation:

• Smaller payloads: Reduce Redis memory usage and network traffic by using a compact binary format.
• Future extensibility: Leverage Jackson as a single serialization framework (shared configuration, annotations, modules) across formats. e.g. JSON and XML.

Implementation Details:

• Added Jackson + MessagePack dependencies.
• Implemented a new Redis serializer.
  • Primary format: MessagePack for all new writes.
  • Backward-compatible reads.
    • Can still deserialize existing Java-serialized objects and JSON values.
• Existing API for Redis access is unchanged. Only different internal serialization mechanism has been updated.

Unit Tests:

• See edu.caltech.ipac.util.serialization.SerializerTest
  • It should cover all current use cases.

Test Instances:
https://firefly-1925-redis-value-messagepack.irsakubedev.ipac.caltech.edu/irsaviewer/
https://fireflydev.ipac.caltech.edu/firefly-1925-redis-value-messagepack/firefly/

All behavior should remain the same as before the change.

[robyww]

Looks good. See my question about JsonAutoDetect

[robyww]

This is pretty verbose. would

@JsonAutoDetect(fieldVisibility = JsonAutoDetect.Visibility.ANY)

since it all defaults to NONE?

[loitly]

I’m not sure whether it defaults to NONE, but when using auto-detect I explicitly want to exclude all getter and setter methods and rely only on the declared fields.