Inscription Notes #4510

This is apropos of #4504.

It should be possible for inscriptions to have features that let inscription owners interact with them, changing their apparent state.

The obvious way to do this is by creating a child inscription, which only the owner can do, which an inscription can then react to by reading its own children. However, this would mean cluttering the list of children and wallet with inscriptions that are essentially protocol messages.

To support this, we should:

1. Add a way for child inscriptions to be created that do not appear in the list of children.
2. Add a way for inscriptions to be inscribed that are not added to the wallet.
3. Allow inscriptions to query such inscriptions.

To implement this:

1. Add --hide / hide: true or --disown / disown: true options when inscribing which hide an inscription from child lists.
2. Add --unbind / unbind: true options when inscribing which unbind an inscription on creation and cause it not to appear in the wallet.
3. Add a recursive endpoint, /r/notes/ID or /r/disowned/ID or /r/hidden/ID for querying such children.