return deterministic user tracking id and remove celeste

[himanshuchawla009]

• Add trackingId query param, use default trackingId if not enabled.
  • Idea of this tracking id in query params is to track user's end to end request flow during a timestamp
  • Default tracking id is deterministic so it also helps in audit trail to search for all logs for a user in all services.
  • This should only be enabled when required for performance testing and debugging because adding query param disables preflight request caching. So by default it should remain off.
• Remove celeste
• Remove network path from tss and rss endpoints (since those endpoints doesnt works for legacy networks)

Future improvements:-

1. Enable tracking per verifier basis (dynamically), we will need to add some persistence in that case. Currently tracking can be enabled only from sdk or by changing env variable.

[chaitanyapotti]

Lgtm