fix: Fix default timeout value.

[CarloWood]

Many callsites don’t pass duration, relying on the default. The way the default was specified was wrong, resulting in an 'undefined' value if no duration is passed instead of 5000.
Passing undefined to setTimeout causes an immediate timeout (in practise a very shortly visible TUI toast UI.

Issue for this PR

Closes #17191

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

It fixes that the default of 5000 is actually used if nothing is passed, instead of getting undefined.

How did you verify your code works?

I run opencode in a container with a network namespace; everything is firewalled, so I got for every attempt to connect some https:// url the vague error "Unable to connect. Is the computer able to access the url?" which showed up so short that there was hardly time to read it.

I could reproduce this simply by testing "test" and hitting enter on a prompt.
After applying this patch that changed to a neat 5 seconds long visible error, as it should.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

If you do not follow this template your PR will be automatically rejected.

[github-actions]

Hey! Your PR title Fix default timeout value. doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

[github-actions]

Thanks for updating your PR! It now meets our contributing guidelines. 👍

[CarloWood]

That failure is unrelated to my fix... In fact, I think my fix fixes what that failure is complaining about: you no longer have to pass something because now the default DOES work.

[kommander]

Well, the type changed so these have to be fixed.

[CarloWood]

Well, the type changed so these have to be fixed.

Still, not related to this one-liner fix. I hope the fact that it says "Some checks were not successful" isn't going to be a reason that no is going to review this patch.

[CarloWood]

Replaced by #18113