[BUG] Incorrect timeout setting for call_and_validate

[gosuvn]

Checklist

• I checked the FAQ section of the documentation
• I looked for similar issues in the issue tracker

Describe the bug
Timeout is in second for call_and_validate function.

To Reproduce
Steps to reproduce the behavior:

Use the function response = case.call(verify=False, timeout=30000)

Expected behavior
Timeout supports to be millisecond but Schemathesis use it as second.
It use millisecond for the default setting, even convert to second back for the exception.
If we pass in millisecond, the timeout will be too long.
If we pass in second, the exception will print out incorrect value.
See :

schemathesis/src/schemathesis/models.py

Line 356 in f87079c

data.setdefault("timeout", DEFAULT_RESPONSE_TIMEOUT / 1000)

Environment (please complete the following information):

• OS: Debian WSL
• Python version: 3.8.10
• Schemathesis version: 3.19.5
• Spec version: 3.0.3

Additional context
We should convert it to second from millisecond like in this commit 3b5c699

[Stranger6667]

That's a design bug I made as it leads to discrepancy:

• call / call_and_validate aim to be thin proxies around the underlying transports, so users can pass any keyword arguments that are supported by the transport as they are. Python's requests expects timeout in seconds.
• Apparently, I thought that curl takes a timeout in milliseconds and implemented it in CLI this way. But it also uses seconds

-m, --max-time Maximum time allowed for transfer

httpie also uses seconds:

--timeout SECOND

So, I think that the better approach would be to change the CLI option, but it will be a breaking change.