Use range union on env triad slots

[pkalita-lbl]

Related to https://github.com/microbiomedata/issues/issues/718. I'll keep the issue open until these changes make it into a released version that is picked up by the submission portal.

Summary

• Upgrade to sheets-and-friends@0.5.3
• Use new features in sheets-and-friends to replace the range of env_broad_scale, env_local_scale, and env_mediumwith an any_of construct that allows either the original enum or a string. DataHarmonizer understands that it should present the enum permissible values in a dropdown menu. But at validation time it accepts either an enum permissible value or a string, which is what the schema says to do.
• Upgrade the version of data-harmonizer used by the interactive testing interface

Testing

• Build the project artifacts with make all
• Start the interactive testing interface with make dh-dev
• Visit the testing interface at http://localhost:5173 and from the toolbar select the SoilInterface template
• In the "broad-scale environmental context" column select an item from the dropdown menu (e.g. "arid biome [ENVO:01001838]"). Click the "Validate" button and verify that the cell is not highlighted in red.
• Updated the cell to a valid that is not part of the dropdown but does otherwise follow the pattern (e.g. "whatever biome [ENVO:123456]"). Click the "Validate" button and verify that the cell is not highlighted in red.
• Update the cell to a string that does not follow the pattern (e.g. "whatever"). Click the "Validate" button and verify that the cell is highlighted in red.

[mslarae13]

Based on a discussion at the metadata meeting, decision was made that we will roll out this change so the env triad populates. On demand we'll generate a report of the env triad terms to evaluate (see https://github.com/microbiomedata/nmdc-schema/issues/2047 to be flushed out soon).

I'd like to get this merged in so I can approve the NEON and MONet submissions. @turbomam can you add your review.