Add unauthenticated Rust Flytekit Remote Client Task endpoints

[austin362667]

Tracking issue

flyteorg/flyte#5344

Why are the changes needed?

This PR aims to be the first subtask that validates the feasibility of replacing Python gRPC with Rust one.

What changes were proposed in this pull request?

As a minimum viable PR, we target at end-to-end testing without authentication, and again it supports Task endpoints only at the present time.

Add a flag enable_rust to the FlyteRemote class. When this flag is true, FlyteRemote will use the rust implementation.

remote_rs = FlyteRemote(Config.auto(), default_project=PROJECT, default_domain=DOMAIN, enable_rust=True)
flyte_task = remote_rs.register_task(
    entity=my_test_task,
    serialization_settings=SerializationSettings(
        image_config=ImageConfig.auto(img_name="flyte-cr.io/image-name:tag")
    ),
    version=VERSION_ID,
)
flyte_task = remote_rs.fetch_task(name=TASK_NAME, version=VERSION_ID)

4 task-related APIs in flytekit/clients/friendly_rs.py and flyrs/src/lib.py,

• create_task()
• list_task_ids_paginated()
• list_tasks_paginated()
• get_task()

The communication between flytekit.remote(Python) flyrs.FlyteRemote(Rust) is throrugh serialization/deserialization as bytes string.

How was this patch tested?

Setup process

Please walk through #2415 .

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

Docs link

[pingsutw]

LGTM, thank you