prototype addition of an editable yaml file for ease of use in extracting ENVO terms via OAK for env triad permissible values

[sierra-moxon]

this PR tries to:

• add a simple yaml file that team members could edit to control the generation of a list of terms from ENVO extracted via OAK (prototyped one replacement makefile target - still work to do to replace broad_scale targets, etc.)
  • and subsequently, use oak via Python instead of wrapping the command-line function
• add tests of the oak extraction and file generation steps
• make the generation runnable from a make command
• separate the config of the ENVO adapter from the config of the terms to extract
• start pulling apart the Makefile into modules
  • should we pull our final control logic (makefile), scripts, extraction logic, and config files into a repo that only has the job of producing these value sets? I think that would help us maintain this logic in "production" mode.

[turbomam]

Awesome. I have added another env_local_set tweaking mechanism since we last met. Can we meet on Zoom to make sure everything is compatible and then do the merge?

[turbomam]

PS I'll be push some more soon, but in a branch, not main