Adjust tee-worker counterpart of pallet-teebag

[Kailai-Wang]

Context

Only relevant extrinsics are kept - (so no shield_funds and unshield_funs), enough refactoring.

Please review (particularly) the pallet-teebag refactoring and node-api for pallet-teebag storage API access

It's a preparation of P-487 (actually, some code is already removed to make it compile).

[linear]

P-485 Adjust tee-worker counterpart of pallet-teebag

[Kailai-Wang]

cc @jonalvarezz it will be a breaking change for client (SDK) as the pallet/extrinsic interface has changed

[Kailai-Wang]

fixes P-10
fixes #1133

[Kailai-Wang]

The lit-resume-worker test fails at the moment, I created an issue P-501

[jonalvarezz]

cc @jonalvarezz it will be a breaking change for client (SDK) as the pallet/extrinsic interface has changed

Yes, quite a breaking change. We'd need to put IDH under maintenance for a few minutes before releasing it.

Btw, will this be released on the original plan of releasing every 3 weeks? So I can plan the client-sdk update accordingly.

[Kailai-Wang]

cc @jonalvarezz it will be a breaking change for client (SDK) as the pallet/extrinsic interface has changed

Yes, quite a breaking change. We'd need to put IDH under maintenance for a few minutes before releasing it.

Btw, will this be released on the original plan of releasing every 3 weeks? So I can plan the client-sdk update accordingly.

I'd prefer an ad-hoc release if the next regular release is distant. However, the majority of IDHub colleagues is on vacation next week so maybe we can't do it in a hurry anyway :(

[Kailai-Wang]

Well mainly the change from teerex to teebag - and the extrinsic/event names have changed.
It affects the registration process, the enclave registry on parachain as well as the callback events (e.g. the famous teerex.ProcessedParentchainBlock event :D )

[jonalvarezz]

I'd prefer an ad-hoc release if the next regular release is distant. However, the majority of IDHub colleagues is on vacation next week so maybe we can't do it in a hurry anyway :(

We can handle that. It is mostly infrastructure so we can definitely do it on behalf of them.

[jonalvarezz]

e.g. the famous teerex.ProcessedParentchainBlock event :D )

Is that one changing names as well? The monitoring service we have relies on it. It'd need update too then

[Kailai-Wang]

Yes it's now teebag.ParentchainBlockProcessed - we'll add more lifecycle events later

[felixfaisal]

LGTM, Tested locally