Allow nested target paths in replace_attribute action

[pkalita-lbl]

Required for https://github.com/microbiomedata/issues/issues/718, but keeping that issue open until the actual submission-schema changes are made.

Summary

The main thing these changes aim to do is provide support for a line like this in the modifications TSV file, where the target of the replace_attribute action is a nested path:

class	slot	action	target	value
SoilInterface	env_local_scale	replace_attribute	any_of.0.range	EnvLocalScaleSoilEnum

While I was at it I took the opportunity to a little overdue refactoring and testing.

Details

• Moved the handlers for each action type into standalone functions that each take the same arguments. These are then grouped into a dict, keyed on the action name. While processing each row of the modification TSV, the appropriate action handler is retrieved from this map and called.
• Updated the handler for the replace_attribute action to accept nested paths. When one is encountered it builds out the necessary intermediate structures in the schema_dict before setting the value. See inline comments for more details. I also fixed a bug in this handler where strings were not being cast into booleans correctly.
• Added a new action named remove_attribute.
• Added unit tests for each action handler function along with a new GitHub Actions workflow to run the unit tests on PRs and merges to main.
• Fixed the poetry-dynamic-versioning setup

[mslarae13]

I tested a submission in dev & it isn't validating. Should this be live in dev & testable? @pkalita-lbl

[turbomam]

@mslarae13 can you please describe what you tried to do and the way in which it failed?

[pkalita-lbl]

Here's where we are right now:

✅ These changes made to sheets_and_friends ✅ New version of sheets_and_friends released ✅ New version of sheets_and_friends used in submission-schema build ✅ New version of submission-schema released 🚫 Bring new version of submission-schema into nmdc-server

I was working on that last step on Tuesday when Eric ran into issues bringing the latest schema version into nmdc-runtime. I put a pause on what I was doing in case there needed to be a new nmdc-schema version released.

[mslarae13]

Ok! Thanks @pkalita-lbl can you let me know when this is in dev then? I think the schema issue was resolved???

[pkalita-lbl]

Yes I can let you know