chore: P-1044 merge all identity tests into one

[higherordertech]

Context

As title

Labels

Please apply following PR-related labels when appropriate:

• C0-breaking: if your change could break the existing client, e.g. API change, critical logic change
• C1-noteworthy: if your change is non-breaking, but is still worth noticing for the client, e.g. reference code improvement

How (Optional)

Testing Evidences

Please attach any relevant evidences if applicable

[linear]

P-1044 Merge CI identity test

[jonalvarezz]

having all the tests in a single place makes sense, thanks @higherordertech

Because of how ts-tests were created, I understand we need to clean up storage with clear_linked_identities. I guess it is ok to have development-only features, but I'd have preferred to re-work ts-tests to for example use random accounts each time instead of requiring a cleanup on every run. I understand it'd be out of scope, too.

[Kailai-Wang]

Thanks!

It's good to go once CI passes - please note we expect the tests to be adjusted again to align with the omni-account usage (very soon, but the effort should not that huge)

[higherordertech]

having all the tests in a single place makes sense, thanks @higherordertech

Because of how ts-tests were created, I understand we need to clean up storage with clear_linked_identities. I guess it is ok to have development-only features, but I'd have preferred to re-work ts-tests to for example use random accounts each time instead of requiring a cleanup on every run. I understand it'd be out of scope, too.

Spot on, I updated the tests to not rely on cli to clear idgraph but just randomize new account for each test case now.