feat: Warn when Work IQ is not configured and the impact of not having it

Current behavior

I tried to use the wiqd agent ask -q "Hello" and it fails because WorkIQ servvice isn't configured in my tenant. Would love some explanation of where I turn that on or CLI to do so. It doesn't explain about installing workiq. don't make me go hunt for it https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/work-iq/cli and do npm install -g @microsoft/workiq

wiqd agent ask -q "Hello"                  pwsh   80  13:37:37 

⚠️  Your tenant does not yet have the WorkIQ service configured.
    Using the Microsoft Graph proxy endpoint as a fallback.

    To enable the direct WorkIQ endpoint (recommended), run:
      workiq auth consent

  Sending query...

  Agent   T_f07a335f-63d4-befd-e0ef-420d50b111be.declarativeAgent
  Query   Hello

──────────────
Agent Response
warn: Microsoft.WorkIQ.WorkIQClientFactory[0]
      WorkIQ endpoint auth failed with consent/SP error. Falling back to Graph proxy. Error: WAM Error
 Error Code: 3399614468
 Error Message: IncorrectConfiguration
 WAM Error Message: (pii)
 Internal Error Code: 508634081
 See troubleshooting: https://aka.ms/msal-net-wam

{"isError":true,"error":"Agent with ID \u0027T_f07a335f-63d4-befd-e0ef-420d50b111be.declarativeAgent\u0027 not found"}
──────────────
 jeremy.thake    jeremy-agent   15.463s⠀   workiq auth consent                        pwsh   80  13:38:22 
workiq: The term 'workiq' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

and doing that

 workiq auth consent     
Consent failed: WAM Error
 Error Code: 3399614468
 Error Message: IncorrectConfiguration
 WAM Error Message: (pii)
 Internal Error Code: 508634081
 See troubleshooting: https://aka.ms/msal-net-wam

Suggested improvement

Make it smoother on environments to install workiq and use it in this scenaario. Especially if my workstation is auth'd to my production tenant, but i've specifically auth'd into my dev M365 tenant environment.

Additional context

No response

Start at the wiqd agent ask warning and fallback flow described in the report, then review the WorkIQ installation and workiq auth consent entry points. Reproduce the missing-command and consent-error scenarios in the issue. Done means the CLI clearly explains the impact of missing WorkIQ, guides installation and configuration, and handles the tenant-authentication scenario more smoothly.