feat: setup server routing

[piotrostr]

• add nginx conf and arrange routing
• drop tls for the sake of nginx-managed tls
• flip back adapter routes
• flip back engine routes
• nginx setup script
• fix engine binary name
• again
• clean up
• fix kit routes
• bump nginx conf
• make nginx setup more versatile
• add cors headers
• validate the config
• cors headers again
• cors headers again
• cors headers yet again
• temporary debug
• fix header parse err
• more verbose err
• debug headers again
• try fix auth
• install redis at last
• point to the right endpoints
• try fix auth
• try fix again
• try debug more output
• try update nginx conf
• try forward header more appropriately
• more verbose output
• again
• again
• add test case for parsing jwt
• new exception type for decoding key read failure
• bump lock
• bump lock
• fixed
• bump gitignore
• add nginx for testing
• add cors
• again
• more relaxed cors
• more cors
• more cors
• wip

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
15679141	Triggered	Generic High Entropy Secret	e0b747fc2cf8adda3494f9d9e1bd80720e184577	privy/src/auth.rs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}