[AUD-1833] Refactor "Get Tracks" endpoint

[rickyrombo]

Description

Updates the "Get Tracks" endpoint:

• Renames "Get Tracks" to "Get Bulk Tracks"
• Adds "permalink" query parameter
• Removes "route", "slug", and "handle" parameters from documentation without breaking backwards compatibility
• Fixes response documentation without breaking backwards compatibility
• Adds support for getting multiple tracks by IDs

Removes new "Get Tracks By Ids" endpoint:

• Double checked that we're not calling it anywhere in AudiusProject repos
• Seems redundant with "Get Bulk Tracks"

Tests

• Verified the Swagger output shows "Get Bulk Tracks" and a list response
• Checked that using slug/handle still gives a single object response (if no routes/permalinks present)
• Checked that using route still works for one or many tracks
• Checked that using ids works for one or many tracks
• Checked that using new permalink param works for one or many tracks

How will this change be monitored? Are there sufficient logs?

❗ looking for ideas here.

[raymondjacobson]

Let's just make sure to soak this well on staging

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets 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 secrets in your pull request

GitGuardian id	Secret	Commit	Filename
3086103	Generic High Entropy Secret	7989a5d	discovery-provider/integration_tests/tasks/test_anchor_program_indexer.py	View secret
3086103	Generic High Entropy Secret	648c889	discovery-provider/integration_tests/tasks/test_anchor_program_indexer.py	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>