Replace tag/status fixtures with factories

[glennmatthews]

Closes: #DNE

What's Changed

• Introduce TagFactory and StatusFactory
• Delete static test fixtures for Tag and Status
• Remove documentation and tooling for working with static test fixtures since we've changed direction.
• Update VLANFactory.name and VRFFactory.name to reduce likelihood of the names appearing by coincidence in page HTML and causing test cases failures as a consequence.
• Revert changes to clear_status_choices that were made in Add RouteTarget and VRF factories. Add TenancyFilterTestCaseMixin and refactor #2514 and instead just remove the tests for this function.

TODO

• Explanation of Change(s)
• Added change log fragment(s) (for more information see the documentation)
• Attached Screenshots, Payload Example
• Unit, Integration Tests
• Documentation Updates (when adding/changing features)
• n/a Example Plugin Updates (when adding/changing features)
• Outline Remaining Work, Constraints from Design

[jathanism]

👀

[jathanism]

I'm realizing in cases like this it's gonna be a tad more optimal to slice the queryset first, and cast to a list second, assuming we have more than a handful of VLAN objects, that is.

For example:

Suggested change

	names = list(VLAN.objects.all().values_list("name", flat=True))[:2]
	names = list(VLAN.objects.all().values_list("name", flat=True)[:2])

Perhaps since we're starting to repeat this pattern a lot as we refactor to use the fixture factories, we might consider factoring it into a test case helper method? Just thinking aloud. Please don't change it right now.

[glennmatthews]

Good thought. Since we've already got this pattern in a bunch of tests after #2479 and #2514, maybe we should get a housekeeping item open to clean up all of these?

[jathanism]

Solid plan.

[jathanism]

#2605

[gsnider2195]

Would this make sense to be a LazyAttributeSequence?

[glennmatthews]

Could do, then the names would be (random color + sequential number) instead of (random color + random number). I don't feel strongly about one versus the other, I just needed to add something because color names alone weren't proving to be unambiguous enough.

[gsnider2195]

My thought was this line would be easier to read as:

name = factory.LazyAttributeSequence(lambda n: f"{faker.Faker().color_name()}{n}")

[glennmatthews]

Easier to read but guarantees that names are globally unique, which isn't actually a requirement of the model.