chore(tags): Allow for lookup via ids vs. name in the API

[hughhhh]

SUMMARY

Previously we the API only supported queries using the names as way of querying tags, I've updated the API to now accept IDs (better pattern) to allow names to have commas. We discovered the issue in testing and took advantage the opportunity to refactor this piece of code, but also leaving tags param for backwards compatibility.

curl 'http://127.0.0.1:54647/api/v1/tag/get_objects/?tagIds=17,12,13' \
-X 'GET' \
-H 'Accept: application/json' \
# ...

TESTING INSTRUCTIONS

1. goto all entities page (http://127.0.0.1:8080/superset/all_entities)
2. see page render with new network call

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[rusackas]

is fetchObjects above this just dead code now? I don't see it being used elsewhere.

[sadpandajoe]

🏷️ preset:2023.47