[Enhancement] Support tag-based entity relationships across the board (guidelines, terms, etc.)

[mc-dorzo]

Motivation

We would like to associate guidelines/variables/glossary with multiple agents. For that, we would like agents to potentially be associated with multiple tags, and guidelines/variables/glossary to be associated with multiple tags instead of singular set as today (which set today is agent_id).

Solution Proposal

• Instead of X_set (e.g., guideline_set -> Sequence[Guideline]), we want to support tags (e.g., guideline -> Sequence[TagId] )
• In Document classes, we should change X_set: str -> X_tags: Sequence[ObjectId]
• Agent-specific items can still work automatically by attaching the tag agent_id:<AGENT_ID> to any entity.
• Agent will also include tags. These tags will be used to fetch relevant items that match the agent's tags.
• API & CLI should support add and remove tags from guideline/glossary/variable/agent

Discussion

@kichanyurd Did I miss something?

[kichanyurd]

Looks good 👍

[mc-dorzo]

FYI, this breaks our current persistence design, in which we maintain a collection of associations between tags and other classes (e.g., customers) to quickly retrieve all customers associated with a specific tag.
Is that acceptable?