Fix GetServURL unit tests for new isSecureDbgSrvUnlocked logic

[Copilot]

Existing GetServURL unit tests assumed VBN builds and any PROD+debug-enabled build could use state-red/swupdate overrides. The new isSecureDbgSrvUnlocked logic restricts this: only eDEV (always) and ePROD with all three conditions met (dbgServices=true + deviceType="test" + LABSIGNED_ENABLED=true) are unlocked.

Existing tests fixed

• VBN state-red/swupdate tests: Removed incorrect isDebugServicesEnabled and filePresentCheck mock expectations — VBN is neither eDEV nor ePROD, so isSecureDbgSrvUnlocked returns false immediately. Tests now expect TR181 recovery/autoexclude fallback via read_RFCProperty.
• PROD + debug-enabled tests: Added getDeviceTypeRFC ("test") and getDevicePropertyData ("true") expectations to satisfy the full three-condition unlock check.
• PROD + debug-disabled tests: Added now-required getDeviceTypeRFC/getDevicePropertyData expectations (default/empty values, unlock still fails correctly).

New tests added

Test	Scenario	Expected outcome
Dev_StateredURL / Dev_SwupdateURL	DEV build	Always unlocked, no RFC checks
Prod_NoLabsigned_StateredFallback	PROD + LABSIGNED_ENABLED=false	Not unlocked → TR181 fallback
Prod_WrongDeviceType_StateredFallback	PROD + deviceType="production"	Not unlocked → TR181 fallback
Prod_PropertyDataFail_StateredFallback	PROD + getDevicePropertyData failure	Not unlocked → TR181 fallback
QA_SwupdateFallback	QA build	Never unlocked → TR181 autoexclude

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.