Make ExportQueue and CollisionFreeMap data human-readable by "fluo scan" command

When users decide to use an the ExportQueue or CollisionFreeMap recipe, the underlying data is stored in a Fluo table in serialized form. This makes it hard for users to view this data when scanning their Fluo table. It would be nice if these recipes provide plugins that made this data human-readable when scanning the Fluo table.

Start by locating the ExportQueue and CollisionFreeMap recipe implementations and the plugin entry point used by the "fluo scan" command. Read how each recipe serializes its Fluo table data and how scan plugins format values. Done means both recipes expose human-readable scan output, with tests covering the displayed data.

Written by the indexing model from the issue text.