Implements #629 - Port-Specific Custom VLAN Tag

[tardoe]

[NF] New feature summary - closes #629

Adds a customVlanTag parameter to the vlanInterface model and plumbs that through to the UI. This allows a member to have a Peering VLAN handed off on a virtualInterface with a customer port-specific tag. This has also been implemented with the provisioning flow to add a customVlanTag field to the generated YAML file.

I've also included a migration that works against previous versions of the installation.

In addition to the above, I have:

• ensured all relevant template output is escaped to avoid XSS attached with <?= $t->ee( $data ) ?> or equivalent.
• ensured appropriate checks against user privilege / resources accessed
• API calls (particular for add/edit/delete/toggle) are not implemented with GET and use CSRF tokens to avoid CSRF attacks

[tardoe]

@nickhilliard @barryo is it worth me fixing the conflicts above and making this implementation work against the new ORM?

What’s the priority on this feature?

[barryo]

I wouldn't just now @tardoe - let's keep this open and @yannrobin and I will review and look to implement this or something like it now that we have v6 out the door. Give us a couple weeks to catch up.

[tardoe]

@barryo @yannrobin Can I get an update on this? I know of at least 3 IXs running custom forks just to have this feature - it makes upgrading for the communal features infinitely harder for them. If you don't have the resources to complete the required changes, please advise me and I can put the time into it.

[shaneshort]

bump, any reason this hasn't been merged? @barryo @nickhilliard