Authorization template: separate custom code in "Client-side custom code" and "Server-side custom code"

[andrea-dintino]

We finally arrived to the point where we need separation of the Authz Server custom code in the Authorization Template, some needs execution server side, and some in the HTML page served to the Wallet.

So we need graphical separation and different export of the two parts:

Client-side custom code with its own "Zencode client-side input (JSON)" (this will replace the existing custom code in pb) -> this will be exported as authz_client_custom_code

Server-side custom code with its own "Zencode server-side input (JSON)" -> this will be exported as authz_server_custom_code

When that is done, didroom_microservices will be updated to accomodate this flow.