Remove explicit dynamic assigner

[SylvainJuge]

Follow-up of #11884

We can now remove most (but not all) usages of typing = typing = Typing.DYNAMIC as it is now the default thanks to #11884

[SylvainJuge]

Closing as removing those leads to other complications which make it not worth to invest for now (thanks @JonasKunz for the investigation) :

• when testing with indy, there is the error java.lang.IllegalStateException: Cannot assign void to class java.lang.Object. This happens if you use Advice.Return with non-DYNAMIC typing while instrumenting void types. Dynamic typing seems to take care of this and to assign null in that case.
• when testing with non-indy, there are problems with advice paramters with readonly=false: Because then the assignment also happens in the other direction, causing static typing to fail