Fix the permission of team's Actions unit issue

[sillyguodong]

close #24449

The unit of Actions should be contorlled not only by repository.DISABLED_REPO_UNITS but also by actions.ENABLED
in the app.ini.
Previously, the permission of the team's Actions unit was not controlled by actions.Enabled. So, even if the user sets actions.Enabled to false, he can still select the permission of the Actions unit for the team.

This PR makes the permissions of the team's Actions unit also controlled by actions.Enabled. Just appendTypeActions into DisabledRepoUnits slice when initializing if actions.Enabled is false.

Changes:

If Actions is set disbaled in app.ini, like below:

[actions]
ENABLED = false

1. If user try to create/edit a team, will prompt user that Actions is disbaled.

2. actions is not displayed in the sidebar on the team details page

[wolfogre]

The packages unit has the same logic, maybe we could follow what it does?

gitea/modules/setting/repository.go

Lines 307 to 309 in 58caf42

	if !rootCfg.Section("packages").Key("ENABLED").MustBool(true) {
	Repository.DisabledRepoUnits = append(Repository.DisabledRepoUnits, "repo.packages")
	}

Actually, I don't like the hard code way of package, but I think we should keep be consistent, or it will be confusing.

[sillyguodong]

The packages unit has the same logic, maybe we could follow what it does?

gitea/modules/setting/repository.go

Lines 307 to 309 in 58caf42

	if !rootCfg.Section("packages").Key("ENABLED").MustBool(true) {
	Repository.DisabledRepoUnits = append(Repository.DisabledRepoUnits, "repo.packages")
	}

Actually, I don't like the hard code way of package, but I think we should keep be consistent, or it will be confusing.

done and tested