Consider renaming options for `AccountTargetNetworkNote`

[partylikeits1983]

As brought up in review comments of #2365, we should consider renaming AccountTargetNetworkNote.

One option is to rename to AccountBoundNetworkNote as pointed out here: #2365 (review)

The goal is to have a name that most clearly explains the use case, a network note that can be consumed only by a single network account.

Some renaming ideas:

• SingleAccountNetworkNote
• AccountExclusiveNetworkNote
• AccountBoundNetworkNote
• AccountTargetedNetworkNote

[PhilippGackstatter]

No matter what we choose, I would try to make the name of the network note type and the name of what is currently NetworkAccountTarget consistent. If we use the "target" terminology, then something like AccountTargetNetworkNote makes sense to me. TargetedNetworkNote is also a nice option I think. For me, this nicely captures that the network note has a target and the attachment helps the note being routed to the correct target/destination.

AccountBoundNetworkNote emphasizes that the note is scoped/restricted to be consumed by the specified account (although notably this is not enforced by the attachment). In that case, I think we should rename NetworkAccountTarget to NetworkAccountBinding or something like that.

Right now, I don't have a strong preference. It would be interesting how everyone else is thinking about the naming.