feat: allow loose matching on primary values after checking for unique

[ltucker]

This updates diodes matching procedure to consider looser matches when no unique match can be found. This attempts a match on the "primary value" for the type when known (often "name" but not always).

• unique matches are considered first and always preferred
• If nothing matches loosely either, the object is considered new
• If more than one object loosely matches, an ambiguity error is raised (these matches are not constrained to be unique and so may be ambiguous depending on NetBox state)

Some caveats:

This can potentially have unintended consequences (though these are in some respect the requested/desired types of actions)

if a "scoped" object (eg an object with an associated tenant, vrf etc) is specified and loosely matches and "unscoped" (eg global) object, the global object may be modified and become scoped rather than creating a new scoped object.

if an "unscoped" object is specified and a scoped object loosely matches the scoped object may be modified instead of creating a new global object.

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
3264	2901	89%	0%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
netbox_diode_plugin/api/matcher.py	86%	🟢
netbox_diode_plugin/api/plugin_utils.py	83%	🟢
netbox_diode_plugin/tests/test_api_diff_and_apply.py	100%	🟢
TOTAL	89%	🟢

updated for commit: 73430a7 by action🐍

[ltucker]

this is missing a test of the ambiguity error I believe

[jajeffries]

Looks good, apart from the test failures :)