Add GA workflow to test Rust Remote without installing Python gRPC

[austin362667]

Tracking issue

flyteorg/flyte#5344

Why are the changes needed?

To add a integration test for the Rust Remote Client, we have to add Github Action Jobs for building and installing compiled Python extension, flyrs, from Rust through PyO3 bindings.

What changes were proposed in this pull request?

Caution

This PR depends on the previous work done in #2414 .
It cannot be executed before #2414 is merged.

We add two CI/CD jobs,

1. build-without-grpcio
   • Run Rust Remote without installing Python grpcio, grpcio-status.
2. build-with-grpcio
   • Make sure the outputs of the Rust Remote and Python remote are the same.

Both of them are only being tested against integration test test_rust_remote.py that installed flyrs via maturin develop (compiled and installed), and we skip tests if not found module flyrs.

How was this patch tested?

1. Run integration test by command:
   pytest tests/flytekit/integration/remote/test_rust_remote.py

2. Github Action has been tested locally (on my personal forked repo's GA CI), please check the following screenshots.

   These two newly added CI jobs should run after rebase onto the previous works flyrs.

Setup process

Caution

This PR depends on the previous work done in #2414 It cannot be merged before #2414 is merged.

Screenshots

1. Run without gRPC, skip tests in test_rust_remote.py if no Python grpc dependencies installed.

2. Run with gRPC to compare the high-level behavior between two different implementations of the Remote Client.

Check all the applicable boxes

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

Related PRs

This PR depends on the previous work #2414.

Docs link