Adding initial LIBRENMS mappings for netutils

[bminnix]

Adding a mapping for LibreNMS values to network_driver values for the initial values in use.

[itdependsnetworks]

Should not be needed, and will likely get reverted.

[bminnix]

The changes to this file are coming from ruff rules. I was just following ruff --fix after I realized there was an issue called out by ruff.

[itdependsnetworks]

Can you link source of this information for ease of future findings?

[bminnix]

Can you link source of this information for ease of future findings?

I'm not sure the best way to go about doing this since there really isn't a great summarized source, suggestions welcomed.

In the current state this is all coming about as follows:

1. The "constants.py" file is created with "os_manufacturer_map" and "manufacturer_os_map" (both manually created (by @bile0026) after inspecting the files/contents) with the intent to create those specific mappings. All values from the LibreNMS code/base are in this os/manufacturer mapping.

2. The non-driver values being added to the LIBRENMS_LIB_MAPPING/REVERSE are ones coming in directly from the devices themselves and being used to map to/from the nautobot network drivers. I believe these device values obtained are all SNMP value based (and how LibreNMS is obtaining device data).

3. The values in LIB_MAPPER dictionaries are just added after seeing the values that were provided by the devices, and any that throw "Manufacturer mapping not found for OS" get added to the mapping then.

We could go through and try to add a mapping entry for each of the os/manufacturer entries, but there really isn't any great source of info for future findings/requirements.

[jeffkala]

Think you'll need to add a bit to the development_script to to make sure proper doc tables are auto generated since this is a new mapping.

netutils/development_scripts.py

Line 37 in b3e13d2

MAPPER = {