[Based on transaction extension 3685] make transaction extension pipeline not rejecting not signed origins

[gui1117]

Based on #3685

Update transaction extensions so that not signed origins are passing throught and correctly refunded.

• payments transaction extensions is done with refund.
  Ideally the transaction extension should be an option, so that we don't need to refund and instead we don't charge when the transaction extension is not used.
• PrevalidateAttests is refactor to have the weight at the correct place.
• CheckNonce is refunded for when nonce is not checked.
  Same ideally Nonce should be Option<Nonce>, so that we can have proper weight ahead of time and not need to do refund.
• bridges transaction extensions, allow not signed origins. But benchmark and weight will be done in another PR

I'm thinking we should be able to support multiple version of transaction extension at the same time in the runtime. So we can easily extend the capability of the transaction extensions.
Then we can have optional transaction payment and optional check nonce easily.

@georgepisaltu

[georgepisaltu]

Looks good so far, let's add a test for each of the transaction payment extensions which checks the NoCharge behavior and asserts the full weight is refunded.

However, we should not merge this change together with phase 1 of extrinsic horizon (Transaction Extension), at least the way it is now.

This is because from the moment the transaction extension PR is merged, general transactions can be constructed. In the current verison of the Transaction Extension PR there is no DenyNone or custom Applyable logic to deny transactions with a None origin.

We need to either:

1. change the behavior in the Transaction Extension PR to disallow transactions with no origin
2. wait for the phase 2 PR to be completed to merge this (in other words, develop this PR further with the other changes)

[gui1117]

We need to either:

1. change the behavior in the Transaction Extension PR to disallow transactions with no origin

2. wait for the phase 2 PR to be completed to merge this (in other words, develop this PR further with the other changes)

I would choose 1.

I was thinking with 2. that ValidateUnsigned will only be deprecated not removed.
And there is still inherent which are bare transaction which dispatch a None origin. Those transaction must be denied in the transaction extension. Either DenyNone or in the DispatchTransaction/CheckExtrinsic implementation in sp-runtime.

We can just remove DenyNone, people can implement it themselves if they have their own implementation of Extrinsic.

[georgepisaltu]

Why does Pre need to be Debug?