This ticket is to require tags to be documented, e.g. by having a "tags documentation" file and rejecting a jstest that has an undocumented tag.

Each test should have a comment above each tag that explains why it's using the tag, but that comment shouldn't need to explain what the tag is for. For example, a test could have "requires_persistence" with comment "This test restarts the tenant migration donor primary", and "requires_persistence" could be documented as "excludes the test from running with the inMemory storage engine."

This would be especially helpful because we often write new jstests by copying old ones, and it's hard to tell if we should carry over all the existing tags.