fwidgen is useful for development and maybe scripting tests. Eventually our packaging infrastructure will need to generate this value as part of producing a corpus of measurement values describing a release. We don't want to force that code to shell out to fwidgen. We should instead provide a function, likely attached to RawHubrisArchive, that generates the FWID for the associated to_binary().