Nautobot 1.5.3 makes test fail

[chadell]

Environment

• Python version: 3.8
• Nautobot version: 1.5.3
• nautobot-netbox-importer version: 1.4.2

Expected Behavior

Unittests pass

Observed Behavior

System check identified no issues (0 silenced).
..........
======================================================================
FAIL: test_imported_data_correctness (nautobot_netbox_importer.tests.test_import.TestImport) (content_type='extras.customfield', ids={'name': 'Custom Text Field A'})
Iterate over all imported data and check its correctness.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/source/nautobot_netbox_importer/tests/test_import.py", line 104, in test_imported_data_correctness
    self.assertEqual(expected_value, actual_value, f"key '{key}' on {model} '{record}' is incorrect")
AssertionError: '' != 'Custom Text Field A'
+ Custom Text Field A : key 'label' on customfield 'Custom Text Field A' is incorrect

======================================================================
FAIL: test_imported_data_correctness (nautobot_netbox_importer.tests.test_import_objectchange.TestImportObjectChange) (content_type='extras.customfield', ids={'name': 'Custom Text Field A'})
Iterate over all imported data and check its correctness.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/source/nautobot_netbox_importer/tests/test_import.py", line 104, in test_imported_data_correctness
    self.assertEqual(expected_value, actual_value, f"key '{key}' on {model} '{record}' is incorrect")
AssertionError: '' != 'Custom Text Field A'
+ Custom Text Field A : key 'label' on customfield 'Custom Text Field A' is incorrect

----------------------------------------------------------------------
Ran 12 tests in 37.242s

Steps to Reproduce

1. invoke unittest

[glennmatthews]

Probably a consequence of nautobot/nautobot#2136:

label is still not a mandatory field on the database model, but the UI now treats it as required, and if left unset when creating a new CustomField or migrating from 1.3, it will default to copying the name value into label.