move DataReceiver to near-vm-errors

[Ekleog-NEAR]

See #9176 for the rationale, near-vm-errors will be merged into
near-vm-runner as soon as circular dependencies are done for.

see #8197

[nagisa]

How do you anticipate disentanging the only(?) direct user of this DataReceiver type – ActionReceipt? Also move that to near_vm_errors? It seems to me like it would be better to group some of those other types into the same PR in this instance.

[Ekleog-NEAR]

I’m not planning on disentangling ActionReceipt yet; currently my goal is to remove the dependency of near-vm-logic on near-primitives, because it blocks the merge of near-vm-errors for circular dependency reasons. And my impression (though I haven’t finalized the PR moving near_primitives::Action to near-vm-errors yet, with it being the last blocker to remove the dep from near-primitives I think) is that I won’t have to touch it for the currently planned merge.

[Ekleog-NEAR]

#9217 concludes what’s needed to remove the dependency from near-vm-logic to near-primitives and thus hopefully finally being able to merge near-vm-errors and near-vm-runner. It confirms I don’t think we need to deal with ActionReceipt yet — TBH I think it’ll probably have to be merged into node-runtime but not before, judging from its current uses