A global environment variable is required for Actions

Feature:
Please make the global environment variable feature available in the Actions script. (like Rules).

Description:
I have heard that Rules is being discontinued and we need to move to Actions.
Currently, I have defined the ClientID and URL of a specific app in the environment variable of Rules and refer to them from multiple Rules scripts. This ClientID is added to the environment variable each time the number of apps increases.

If we try to perform the same operation with Actions secret, we will need to add each ClientID to the definition of each Actions secret each time the number of ClientIDs increases, so the operational load will be higher than with Rules.

Therefore, I believe a global environment variable is necessary to move from Rules to Actions.

Use-case:
It would be useful if Actions could be operated in the same way as Rules.