feat: ZETA token support on Solana

[s2imonovic]

Adding support for ZETA token on Solana.

Closes: #121

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0.83333% with 119 lines in your changes missing coverage. Please review.
✅ Project coverage is 2.77%. Comparing base (52f3f4d) to head (4656135).

Files with missing lines	Patch %	Lines
programs/zeta-token/src/instructions/admin.rs	0.00%	35 Missing ⚠️
programs/zeta-token/src/instructions/mint.rs	0.00%	32 Missing ⚠️
programs/zeta-token/src/instructions/burn.rs	0.00%	24 Missing ⚠️
programs/zeta-token/src/lib.rs	4.54%	21 Missing ⚠️
programs/zeta-token/src/contexts.rs	0.00%	4 Missing ⚠️
programs/zeta-token/src/state.rs	0.00%	2 Missing ⚠️
programs/zeta-token/src/errors.rs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##            main    #126      +/-   ##
========================================
- Coverage   2.98%   2.77%   -0.22%     
========================================
  Files         16      23       +7     
  Lines       1107    1227     +120     
========================================
+ Hits          33      34       +1     
- Misses      1074    1193     +119     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gitguardian]

⚠️ 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
19511594	Triggered	Generic High Entropy Secret	b53de72	Anchor.toml	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.}

[sherlock-ai-beta]

Sherlock AI

Thank you for using Sherlock AI!

Security Review Unavailable: Your account doesn't have an active subscription. To enable automated security reviews on your pull requests, please visit https://ai.sherlock.xyz to set up your subscription.

Once activated, Sherlock AI will automatically analyze your code changes and provide detailed security findings directly in your pull requests.

Need help? Reach out to us at [email protected].