gitea: Organization-wide projects bugs

Description

At the moment, organization-wide projects are riddled with bugs, based on preliminary user feedback from 1.19.0-rc1: They are

• no one (not even the site admin) can edit/delete org projects, see screenshots 1 and 3
• repo projects allow to set the card preview type during creation. Organization projects don’t, see screenshots 5 and 6
• Org projects ignore the column color, see screenshots 1 and 2, the right column should have the color #ff0000.

These issues can be fixed by sharing the code of repo projects with the organization projects.

Furthermore, the following issues are present:

• The organization Projects tab misses quite a few tabs as well as the organization settings, see screenshots 1, 3, and 5.
• When creating an org project, and adding a second column
  • and setting the second one as default, the initially created column disappears permanently, until the second column is deleted again. Happens both for repo- and org-projects. (#23401)
  • only the second column can be edited, the first one can’t, see screenshot 1 and 2. Happens both for repo- and org-projects
• If a repo disables projects, its issues cannot be assigned to org-wide projects either. While the current logic for that is clear (if isPackagesEnabled <list available projects> end), this would probably still be useful to implement.
• Both organization and repo projects cannot edit the column color anymore
• If you click on the PR that closed an issue inside an org-wide project, you get redirected to $URL/pull/$ID instead of $URL/$USER/$REPO/pull/$ID

Screenshots

Screenshot 1: Org project appearance

Screenshot 2: Repo project appearance

Screenshot 3: org repo projects list

Screenshot 4: Repo projects list

Screenshot 5: New org project

Screenshot 6: New repo project

Gitea Version

1.20.0+dev-90-gea7f0d6fc

Can you reproduce the bug on the Gitea demo site?

Yes

Operating System

Linux

Browser Version

Firefox 110.0