Support configuration variables on Gitea Actions

[sillyguodong]

Co-Author: @silverwind @wxiaoguang
Replace: #24404

See:

• defining configuration variables for multiple workflows
• vars context

Related to:

• protocol: https://gitea.com/gitea/actions-proto-def/pulls/7
• act_runner: https://gitea.com/gitea/act_runner/pulls/157
• act: https://gitea.com/gitea/act/pulls/43

Screenshoot

Create Variable:

Workflow:

  test_vars:
    runs-on: ubuntu-latest
    steps:
      - name: Print Custom Variables
        run: echo "${{ vars.test_key }}"
      - name: Try to print a non-exist var
        run: echo "${{ vars.NON_EXIST_VAR }}"

Actions Log:

---

This PR just implement the org / user (depends on the owner of the current repository) and repo level variables, The Environment level variables have not been implemented.
Because Environment is a module separate from Actions. Maybe it would be better to create a new PR to do it.

[JakobDev]

You should also implement this on the User Level

[silverwind]

Row vertical padding is unequal. Source of the problem may be a polluted style we have on some of these tables where first row has more padding to hold a description text. Should be solveable via some gt-py-3 classes on the rows I assume.

[silverwind]

Regarding field names, do I understand that we have now Name/Data in database and Name/Value in UI, right? Is it like that for both secrets and variables?

[sillyguodong]

Regarding field names, do I understand that we have now Name/Data in database and Name/Value in UI, right? Is it like that for both secrets and variables?

yes it is