[WIP] Separate remote signal functions

[mao3267]

Tracking issue

Closes flyteorg/flyte#3459

Why are the changes needed?

Currently, the set_signal function can be used to handle three distinct actions: approving, rejecting, and providing input for gates. However, this implementation is not intuitive for users. To enhance clarity and usability, we propose splitting the set_signal function into three separate functions: approve, reject, and set_input. This change will make the functionality more straightforward and user-friendly during coding.

What changes were proposed in this pull request?

1. Added three functions in FlyteRemote, which are approve, reject, and set_input, providing certain signals or values for gates.
2. Do integration tests to make sure it works.

How was this patch tested?

1. Integration tests are added.

Setup process

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

[codecov]

Codecov Report

Attention: Patch coverage is 15.00000% with 17 lines in your changes missing coverage. Please review.

Project coverage is 38.33%. Comparing base (3f0ab84) to head (6bda0f8).
Report is 4 commits behind head on master.

Files with missing lines	Patch %	Lines
flytekit/remote/remote.py	15.00%	17 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #2933       +/-   ##
===========================================
- Coverage   76.33%   38.33%   -38.01%     
===========================================
  Files         199      199               
  Lines       20840    20873       +33     
  Branches     2681     2685        +4     
===========================================
- Hits        15908     8001     -7907     
- Misses       4214    12659     +8445     
+ Partials      718      213      -505     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.