Named outputs (#485)

```
import flyte.remote

r = remote.Run.get(...)
o = r.outputs()
print(r.named_outputs())
```

Output;
```
{o0: ...,  o1: ...}
```

Signed-off-by: Ketan Umare <[email protected]>
Co-authored-by: Ketan Umare <[email protected]>

Serving improvements (#478)

Signed-off-by: Ketan Umare <[email protected]>
Co-authored-by: Ketan Umare <[email protected]>

GB10 added to sdk (#452)

Signed-off-by: Ketan Umare <[email protected]>
Co-authored-by: Ketan Umare <[email protected]>

de-duplicate files in app code bundling (#444)

Signed-off-by: Niels Bantilan <[email protected]>

Working example of multi folder structure with just pythonpath (#430)

* Insert root dir instead of cwd into sys.path, but these are the same
in most cases.
* Fix the deploy logic to rely on import_module directly which avoids
duplicate loading and respects parent packages.

---------

Signed-off-by: Ketan Umare <[email protected]>
Signed-off-by: Yee Hing Tong <[email protected]>
Co-authored-by: Ketan Umare <[email protected]>
Co-authored-by: Yee Hing Tong <[email protected]>

[Bug] Nested schema type detection for reference tasks does not work (#…

…426)

Add idle timeout to code server instead of relying on heartbeat file (#…

…413)

Signed-off-by: Kevin Su <[email protected]>

Install local project in uv script (#372)

This pull request introduces support for handling local Python projects
specified via `file://` dependencies in uvscript files, improving image
building workflows to include these projects as layers. The changes
parse and separate standard dependencies from local project references,
update image layer construction to include these projects, and ensure
proper hashing and Dockerfile generation for reproducible builds.


- Updated `parse_uv_script_file` in `uv_script_parser.py` to distinguish
between standard dependencies and local projects (`file://`), storing
them separately in the `UVScriptMetadata` dataclass. This enables
downstream logic to handle local projects distinctly from regular
dependencies.
[[1]](diffhunk://#diff-f52f9cd55e56dfa99ad1fec9fbae44f5439666a95c56d0ad8594b499ef455657R19)
[[2]](diffhunk://#diff-f52f9cd55e56dfa99ad1fec9fbae44f5439666a95c56d0ad8594b499ef455657R48-R56)
- Use the with_uv_project to install the local project

```python
# /// script
# dependencies = [
#    "polars",
#    "ty",
#    "mypy",
#    "flyte @ file:///Users/kevin/git/flyte-sdk",
# ]
# ///

import polars as pl

import flyte

env = flyte.TaskEnvironment(
    name="hello_world",
    image=flyte.Image.from_uv_script(__file__, name="flyte", registry="ghcr.io/flyteorg"),
)


@env.task
async def create_dataframe() -> pl.DataFrame:
    return pl.DataFrame(
        {"name": ["Alice", "Bob", "Charlie"], "age": [25, 32, 37], "city": ["New York", "Paris", "Berlin"]}
    )


@env.task
async def print_dataframe(dataframe: pl.DataFrame):
    print(dataframe)


@env.task
async def workflow():
    df = await create_dataframe()
    await print_dataframe(df)


if __name__ == "__main__":
    flyte.init_from_config()
    r = flyte.run(workflow)
    print(r)

```

---------

Signed-off-by: Kevin Su <[email protected]>

Add description to task deploy (#314)

Signed-off-by: Alex Wu <[email protected]>
Co-authored-by: Ketan Umare <[email protected]>

Introduce _U_INSECURE env var (#347)

This pull request enhances the `init_in_cluster` initialization logic to
support explicit insecure connection overrides via an environment
variable, and adds comprehensive tests to ensure correct behavior for
various endpoint and insecure configurations.

**Enhancements to insecure connection handling:**

* Added support for the `_U_INSECURE` environment variable in
`init_in_cluster` to explicitly override insecure connection detection
logic. If set, this variable determines the value of the `insecure`
parameter regardless of endpoint auto-detection.
[[1]](diffhunk://#diff-538f74d7f61b28e182d9c7242e7fff8921498c733c8ae654231daec768cee455R347)
[[2]](diffhunk://#diff-538f74d7f61b28e182d9c7242e7fff8921498c733c8ae654231daec768cee455R365-R366)

**Testing improvements:**

* Introduced a new test class `TestInitInCluster` in
`test_initialize.py` to verify the behavior of `init_in_cluster` under
different combinations of endpoints and insecure settings, including
environment variable overrides.
* Added tests to ensure that insecure auto-detection works for
docker/localhost endpoints and that the `_U_INSECURE` environment
variable always takes precedence when set.
* Updated imports in the test suite to include `init_in_cluster`.

---------

Signed-off-by: Kevin Su <[email protected]>
Signed-off-by: pmahindrakar-oss <[email protected]>
Co-authored-by: pmahindrakar-oss <[email protected]>