Standardize how major nodes are embedded in other nodes, e.g. asset moves, moves oracles

A standalone move/asset/etc should be content-complete without specifying a whole Datasworn tree.

tables are commonly embedded in moves
- these should be distinct from external tables that are relevant to a move, like "Story Clue" in SF
Some moves (Ask the Oracle) have multiple embedded tables
Asset moves
There's at least one example of a table being embedded in an asset (Parrot)
Should these nodes have IDs? How should they be constructed?
- asset moves need to be referenced occasionally. if they don't have IDs, they should have some other means of pointing to them

rsek / datasworn