CircuitMaintenance "name" should probably include provider as well as maintenance_id

[glennmatthews]

Environment

• Nautobot version:
• nautobot-circuit-maintenance version:

Proposed Functionality

As and when this plugin is used with an ever-growing set of providers sending maintenance notifications, it becomes increasingly likely that two different providers will send maintenance notifications that happen to use the same maintenance ID number/string. (Consider the case of two providers each sending their very first maintenance notification, and both choosing to identify it as maintenance id "00000001"). Because we use the maintenance_id as the globally-unique name of the CircuitMaintenance model instances, these two disparate sets of maintenance notifications would inadvertently be merged into a single CircuitMaintenance instance named 000000001, which is almost certainly undesirable.

To avoid collision between providers in this fashion, we should probably include the notification provider value in addition to the maintenance_id in constructing the CircuitMaintenance name.

Use Case

[chadell]

@glennmatthews +1

[chadell]

Addressed in #81