Investigate how to handle breaking changes in the storageEngine option in the create command

As part of WT-6678, the huffman_key option was removed from WT_SESSION::create(). This can be passed through on the create command via the storageEngine option. This has ramifications both for create commands formed from metadata.json files as well as create oplog entries. A collection from a version <4.4.3 that uses Huffman encoding for keys will not be able to be created on versions >=4.4.3. There are several options for dealing with this:

1. Do nothing. Users must use --noOptionsRestore as a workaround. This is not the best experience for users.
2. Ignore invalid options. This is potentially unsafe.
3. Blanket ignore invalid options when the user sets a flag to do so.
4. Convert legacy options in the same way we convert legacy index options - this will require the most work and maintenance.

I think 3 might be the best way forward here.