make error types more precise for transaction method

[mberndt123]

I ran into a situation where I needed these more precise error types, so I thought I'd propose them upstream.

I have also noticed that in ZioJdbcUnderlyingContext#transaction, if the passed action f fails, the error will always be wrapped in Cause.die, even if the rollback succeeds. I think that's a bug and therefore fixed it, and it has the nice additional benefit of getting rid of the <: Throwable constraint on the error type. But it is arguably an incompatible change of behaviour (like many bug fixes), so I thought I'd point it out.

Turns out I actually misread the code here, the error handling was working fine.

[mberndt123]

I just noticed that this seems to be the same as #192. So apparently I'm not the only one who wants this. Any chance we can make this happen?

[li-nkSN]

@khajavi

Resolves

• Running an invalid query can throw an IllegalStateException #295 (IllegalStateException escaping error channel) — by removing the Cause.die
  wrapping, typed errors stay in the error channel
• Decoding a json/jsonb column directly to a type throws IllegalArgumentException outside of the error channel #215 (partially) — decode failures that happen within a transaction block will now
  stay in the error channel. However, decode failures outside transactions are a
  separate code path not addressed here
• Preserve existing errors when using transaction #192 — fully superseded by this PR

[mberndt123]

@li-nkSN
Is there anything I can help with to push this forward?

[li-nkSN]

@mberndt123 until I work something out regarding having write access to the core ZIO quill module. If you'd like to have a code review and PR. You may make a PR on li-nk zio-protoquill https://www.reddit.com/r/scala/comments/1rnhrea/bastard_quill_protoquilll_now_available/ . I am also available to discuss on the ZIO discord.