Update ChatCraftCommand::isCommand() criteria for slash function

[rjwignar]

This fixes #500.
The issue encountered above is due to ChatBase interpreting a non-slash command (in this case, a filepath in an error message) as a slash command:

isCommand() currently treats every prompt starting with a forward slash as a potential slash command, then either tries to execute the slash command or parse the invalid command to notify the user (i.e [invalid command] is not a valid command!).

This PR reuses the parseCommand() Regex in isCommand() so things like filepaths aren't treated as a potential slash command:

chatcraft.org/src/lib/ChatCraftCommand.ts

Lines 10 to 12 in f7b2803

	static parseCommand(input: string): { command: string; args: string[] } | null {
	const match = input.match(/^\/(\w+)(?:\s+(.*))?$/);
	if (!match) return null;

How to Test

• Test every existing slash command in the preview and confirm they still work
• Copy/paste the codeblock from the Issue description into a new chat and confirm it is sent as a message analyzed by the LLM.

Potential Issue

I think this is a step in the right direction, but the Regex in the new isCommand() is not perfect.
If the user enters a slash command containing a non-word (special) character, it will be sent to the LLM:

[cloudflare-workers-and-pages]

Deploying chatcraft-org with    Cloudflare Pages

Latest commit:	3e35593
Status:	✅  Deploy successful!
Preview URL:	https://5a483f39.console-overthinker-dev.pages.dev
Branch Preview URL:	https://issue-500.console-overthinker-dev.pages.dev

View logs

[humphd]

ship it