QN: Improve Metaprotocol transactions error handling

As pointed out by [Lezsek](https://github.com/Joystream/joystream/pull/4517#discussion_r1086299357), we need improved & efficient implementation of error handling logic for metaprotocol txs which include features like `comments/reactions`, `videoCategory`, `channelpayment`, `apps` etc.

Further ...
> Going forward it would be good to make metaprotocol transaction errors just enum variants instead of storing the metaprotocol error message in the database, as this would eventually become a lot of wasted storage, and it's unproportionally cheap to spam QN database this way. The frontend could decide what kind of error message to display based on the error code/variant instead. Also it would be language-agnostic approach