Review the enclave registration process

[Kailai-Wang]

Context

The last modification regarding enclave registration in worker-main won't change the logic, because trusted_url differs each time although MRENCLAVE is identical, is this intended?

litentry-parachain/tee-worker/service/src/main.rs

Lines 544 to 554 in a56a56b

	Ok(Some(value)) => {
	if value.mr_enclave.to_vec() == mrenclave && value.url == trusted_url {
	// After calling the perform_ra function, the nonce will be incremented by 1,
	// so enclave is already registered, we should reset the nonce_cache
	enclave
	.set_nonce(nonce)
	.expect("Could not set nonce of enclave. Returning here...");
	found = true;
	info!("fond enclave: {:?}", value);
	break
	}

We might need to ask Integritee why such a registration process is implemented, it seems more intuitive to have MRENCLAVE as key and a list of workers as (sub)-values.

---

✔️ Please set appropriate labels and assignees if applicable.

[Kailai-Wang]

Please note if we want to change it we have to consider some implicit consequences, e.g. when search_peers it looks for all registered enclaves (even with duplicated MRENCLAVE) to find all worker-URLs:

litentry-parachain/tee-worker/service/src/worker.rs

Lines 150 to 161 in a56a56b

	for enclave in enclaves {
	// FIXME: This is temporary only, as block broadcasting should be moved to trusted ws server.
	let enclave_url = enclave.url.clone();
	let worker_api_direct = DirectWorkerApi::new(enclave.url);
	let untrusted_worker_url =
	worker_api_direct.get_untrusted_worker_url().map_err(|e| {
	error!(
	"Failed to get untrusted worker url (enclave: {}): {:?}",
	enclave_url, e
	);
	e
	})?;

[github-actions]

❗ This issue is stale because it has been open for 60 days with no activity.
Remove Stale label or update it, otherwise this issue will be closed in 7 days.
@litentry/parachain

[github-actions]

❗ This issue is stale because it has been open for 60 days with no activity.
Remove Stale label or update it, otherwise this issue will be closed in 7 days.
@litentry/parachain

[felixfaisal]

Hey @Kailai-Wang
Could this issue be related to this - #1820