Closes #17608: Adds L2VPN.status field

[jnovinger]

Fixes: #17608

• adds L2VPN.status field with L2VPNStatusChoices as choices
• adds migration for L2VPN.status
• updates forms and filtersets for L2VPN.status
• updates UI views (tables and detail template) and API serializer for L2VPN.status
• updates L2VPNIndex to display status in results
• fixes tests to use new L2VPN.status field

[jnovinger]

@arthanson , since you won the review lottery: any guidance on what types of fields should be added to a model's clone_fields attribute?

[jnovinger]

Doh, just realized I forgot to update the model docs. Will get that momentarily. Done

[arthanson]

@arthanson , since you won the review lottery: any guidance on what types of fields should be added to a model's clone_fields attribute?

There isn't a set rule - It's used for create and add another for defaulting fields when entering many items, so generally anything that isn't a unique constraint or you will probably change anyways (name, description, position). Status is generally included in cloned_fields, if not probably either a specific reason or an oversight.

[arthanson]

Looks good - should add a test to test_filtersets and maybe test_api as well as it is a required field so not just testing the default.