Add an IdentifiabilityTag component

[allisonking]

Closes #702

Code Changes

• Adds a component for IdentifiabilityTag
• Adds styling to data qualifier objects

Steps to Confirm

• Visit http://localhost:3000/dataset/demo_users_dataset

Pre-Merge Checklist

• All CI Pipelines Succeeded
• Documentation Updated:
  • documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
  • documentation issue created (tag docs-team to complete issue separately)
• Issue Requirements are Met
• Relevant Follow-Up Issues Created
• Update CHANGELOG.md

Description Of Changes

Important caveat: right now I am hardcoding the taxonomy based on the default taxonomy. I could pull this instead from the endpoint to any data qualifiers the user has added, but I'd need some guidance on what color non-default ones should be, and what label they should have. Label could perhaps be the last field in the dot notation? I'm guessing that ideally a user could choose their color/label, but then we would need an interface for them to be able to select that too. Or for color, wild idea, maybe we could do a yellow - red gradient based on how many dots the data qualifier has, since at least for the ones we have so far, the more nested it is, the more identifying the data is 🤔 In any case, depending on what we decide, we'll want another ticket separate from this one for it. FYI @mfbrown

[ThomasLaPiana]

@allisonking i like this!

An idea for the color-coding...maybe we could hash the string and convert that to a hex color code somehow? I guess that would go against the idea of having red = danger though?

[LKCSmith]

🎉