Implement configurable exclusion of deprecated primitives about parsec

[ionut-arm]

We could have a trait for example with a method fn bool is_deprecated(&self) (to be call on an OpXXX or on a NativeOperation) to check if the operation contains deprecated parameters or not.

I like the idea, but is_deprecated on an operation implies that the operation itself is deprecated. Maybe something like is_allowed which would call an is_deprecated on the native KeyAttributes structure? We'll have to think well where we provide these checks and where we plan to enforce them.

[hug-dev]

I like the idea of deprecated primitives rejected by default.
We could have a trait for example with a method fn bool is_deprecated(&self) (to be call on an OpXXX or on a NativeOperation) to check if the operation contains deprecated parameters or not.
It would be more secure to allow specific deprecated parameters instead of allowing them all!

[hug-dev]

Right, because in the end all the security parameters are in the key attributes themselves.