feat(taxonomy): implement TaxonomyCard component with competency and tags icons

[javoconsultant]

Description

Supporting information

openedx/openedx-core#616

Testing instructions

1. Open Studio Home.
2. Click the Taxonomies tab.
3. On the taxonomy list page, check each taxonomy card's header: it should show an icon before the taxonomy name
   - the target/competency icon for taxonomies of type Competency
   - the tag icon for taxonomies of type Tags
4. For a taxonomy with no known type (or one the API doesn't return a type for), confirm it still shows the tag icon as the default, rather than no icon.
5. On a card with a long name, confirm the title still truncates properly next to the icon (ellipsis) and hovering shows the full name in a tooltip.
6. Create a new taxonomy via Import to confirm the type selection feeds the icon shown afterward:
   - Click Import, upload a valid CSV/JSON file, and continue to the taxonomy details step.
   - Confirm a Taxonomy Type dropdown is present with Tags (default) and Competency options.
   - Select Competency, fill in name/description, and finish the import.
   - Back on the taxonomy list, confirm the new card shows the competency icon.
   - Repeat once more leaving Tags selected, and confirm that card shows the tag icon instead.

Other information

Dependencies:
#3208

Best Practices Checklist

We're trying to move away from some deprecated patterns in this codebase. Please
check if your PR meets these recommendations before asking for a review:

• Any new files are using TypeScript (.ts, .tsx).
• Avoid propTypes and defaultProps in any new or modified code.
• Tests should use the helpers in src/testUtils.tsx (specifically initializeMocks)
• Do not add new fields to the Redux state/store. Use React Context to share state among multiple components.
• Use React Query to load data from REST APIs. See any apiHooks.ts in this repo for examples.
• All new i18n messages in messages.ts files have a description for translators to use.
• Avoid using ../ in import paths. To import from parent folders, use @src, e.g. import { initializeMocks } from '@src/testUtils'; instead of from '../../../../testUtils'

[openedx-webhooks]

Thanks for the pull request, @javoconsultant!

This repository is currently maintained by @bradenmacdonald.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

❌ Patch coverage is 99.56140% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 95.93%. Comparing base (16e19f1) to head (5d2a0f1).
⚠️ Report is 3 commits behind head on master.

Files with missing lines	Patch %	Lines
src/taxonomy/import-tags/steps/UploadStep.tsx	96.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3226      +/-   ##
==========================================
+ Coverage   95.92%   95.93%   +0.01%     
==========================================
  Files        1397     1409      +12     
  Lines       33581    33664      +83     
  Branches     7947     7956       +9     
==========================================
+ Hits        32214    32297      +83     
- Misses       1308     1309       +1     
+ Partials       59       58       -1     

☔ View full report in Codecov by Harness.
📢 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.