Inline script metadata ignored when using `uv run -m`

`uv run -m` will not respond to PEP 723 inline script metadata that is included in the script module. My motivating use case is that I typically have some developer and CI conveniences wrapped up in a `click` script with lots of subcommands. I want it to run in an isolated Python venv which only needs `click` installed, not the project's venv. The inline script metadata with `uv run` works great for this. However, I usually implement this in a package with a `__main__.py` script (I factor some things out like configuration into a separate module and might have some data files; a package works great to isolate all of this to keep it tidy from the rest of the project). `uv run -m` does not seem to read the inline script metadata implemented in the `__main__.py` (or other modules run via `-m`).

It's entirely possible that this is not possible if you need the Python env already set up to dereference the `package.module` name to find the actual file. If that is the case, this limitation would be good to document.

Thank you!

```
❯ uv --version
uv 0.4.24 (b9cd54913 2024-10-17)

❯ tree
.
└── foo
├── __init__.py
├── __main__.py
└── script1.py

2 directories, 3 files

❯ cat foo/script1.py
# /// script
# dependencies = [
# "click"
# ]
# ///

import click

@click.command()
def cli():
click.echo("Hello, world, from script1!")

if __name__ == "__main__":
cli()

❯ cat foo/__main__.py
# /// script
# dependencies = [
# "click"
# ]
# ///

import click

@click.command()
def cli():
click.echo("Hello, world, from __main__!")

if __name__ == "__main__":
cli()

❯ uv run foo/script1.py
Reading inline script metadata from: foo/script1.py
Hello, world, from script1!

❯ uv run -m foo.script1
Traceback (most recent call last):
File "/Users/rkern/Library/Application Support/uv/python/cpython-3.10.14-macos-x86_64-none/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/Users/rkern/Library/Application Support/uv/python/cpython-3.10.14-macos-x86_64-none/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/Users/rkern/scratch/uv-m-bug/foo/script1.py", line 8, in
import click
ModuleNotFoundError: No module named 'click'

❯ uv run -m foo
Traceback (most recent call last):
File "/Users/rkern/Library/Application Support/uv/python/cpython-3.10.14-macos-x86_64-none/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/Users/rkern/Library/Application Support/uv/python/cpython-3.10.14-macos-x86_64-none/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/Users/rkern/scratch/uv-m-bug/foo/__main__.py", line 8, in
import click
ModuleNotFoundError: No module named 'click'
```

Reproduce the issue with the shown foo/__main__.py and foo/script1.py examples, comparing `uv run script.py` with `uv run -m package.module`. Start by tracing the `uv run -m` entry point and how PEP 723 metadata is discovered; done means inline dependencies are honored for modules, or the limitation is clearly documented if that is not possible.

Written by the indexing model from the issue text.