copilot --resume no longer allows new session with deterministic id

[mcaden]

Describe the bug

copilot --help specifically states:

# Start a new session with a specific UUID
$ copilot --resume=0cb916db-26aa-40f2-86b5-1ba81b225fd2

Until today, this worked fine. However, it now results in:

Error: No session, task, or name matched '0cb916db-26aa-40f2-86b5-1ba81b225fd2'.

To resume by session or task ID:  copilot --resume=<id>
To resume by name:                copilot --resume=<name>
To name a new session:            copilot --name=<name>
To pick from existing sessions:   copilot --resume

This changes behavior and is counter to what exists in the help.

Affected version

GitHub Copilot CLI 1.0.49-6

Steps to reproduce the behavior

1. generate a new guid that you don't have a session for.
2. Attempt to launch with copilot --resume <session guid>

Expected behavior

It is expected that copilot will start a new session and use the provided GUID. Instead, it fails and provides an error.

Additional context

No response

[LangSensei]

+1

[milope]

+Many :). This appears to have impacted many folks in our team as well