Module rename breaks driver in default consys.db

[BillBrown341]

Description

When using the default connected systems database (consys.db), updating a module name after the driver has been started causes errors and prevents the driver from restarting with the new name.

This behavior is inconsistent with system driver databases, where module names can be updated multiple times without impacting driver functionality.

Steps to Reproduce

1. Initialize a node
2. Use the default connected systems database (consys.db)
3. Create and configure a driver
4. Start the driver
5. Update Module Name
6. Select Apply Changes

Expected Behavior

• The module name can be updated at any time (before or after driver start)
• The driver should restart successfully using the updated module name

Comparison Case (Works as Expected)

When using a System Driver Database instead of the default consys.db:

• Module names can be updated multiple times
• The driver continues to restart and function correctly

Acceptance Criteria

Research and resolve why renaming a module after driver startup causes restart failures in the default consys.db, ensuring consistent module rename behavior across all database configurations

Video Reproduction:

ConSys.db.Module.Name.Issue.mp4

[kalynstricklin]

opensensorhub#348