Reject transactions that consume fee notes

Only the batch builder is allowed to consume these.

Otherwise we would allow:

1. tx a emits fee note a'.
2. tx b emits fee note b' but also consumes (aka steals) a'. This is possible because fee notes are floating.

This would lead to confusing situations in the mempool where a fee note would be attempted to consume multiple times; or in the case where both a & b land in the same batch, that the batch builder doesn't even see a'.

The simplest short term patch is to simply disallow such transactions.