Refactor event and session column names to camelCase

- Updated test cases to reflect new column names (eve_MAC -> eveMac, eve_DateTime -> eveDateTime, etc.) across various test files.
- Modified SQL table definitions in the database cleanup and migration tests to use camelCase naming conventions.
- Implemented migration tests to ensure legacy column names are correctly renamed to camelCase equivalents.
- Ensured that existing data is preserved during the migration process and that views referencing old column names are dropped before renaming.
- Verified that the migration function is idempotent, allowing for safe re-execution without data loss.

test/scan/test_field_lock_scan_integration.py

@@ -117,12 +117,12 @@ def scan_db_for_new_devices():
     cur.execute(
         """
         CREATE TABLE Events (
-            eve_MAC TEXT,
-            eve_IP TEXT,
-            eve_DateTime TEXT,
-            eve_EventType TEXT,
-            eve_AdditionalInfo TEXT,
-            eve_PendingAlertEmail INTEGER
+            eveMac TEXT,
+            eveIp TEXT,
+            eveDateTime TEXT,
+            eveEventType TEXT,
+            eveAdditionalInfo TEXT,
+            evePendingAlertEmail INTEGER
         )
         """
     )
@@ -130,14 +130,14 @@ def scan_db_for_new_devices():
     cur.execute(
         """
         CREATE TABLE Sessions (
-            ses_MAC TEXT,
-            ses_IP TEXT,
-            ses_EventTypeConnection TEXT,
-            ses_DateTimeConnection TEXT,
-            ses_EventTypeDisconnection TEXT,
-            ses_DateTimeDisconnection TEXT,
-            ses_StillConnected INTEGER,
-            ses_AdditionalInfo TEXT
+            sesMac TEXT,
+            sesIp TEXT,
+            sesEventTypeConnection TEXT,
+            sesDateTimeConnection TEXT,
+            sesEventTypeDisconnection TEXT,
+            sesDateTimeDisconnection TEXT,
+            sesStillConnected INTEGER,
+            sesAdditionalInfo TEXT
         )
         """
     )