Last visited repos header shows repos which never have been visited

[zc-devs]

Component

web-ui

Describe the bug

I see repos, that I have never visited in the last visited repos block.

If you never visited a repo it shows the first 4 repos from the "general" list (probably sorted by last pipeline time)

Steps to reproduce

1. Prepare domains

192.168.1.11	wp.local
192.168.1.11	gitea.local

2. Install Gitea

services:
  gitea:
    image: docker.io/gitea/gitea:1.22.6
    container_name: gitea
    environment:
      - USER_UID=1000
      - USER_GID=1000
    volumes:
      - ./gitea:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    networks:
      - gtwp
    ports:
      - "3000:3000"
      - "222:22"
networks:
  gtwp:

3. Open Gitea in Firefox in Incognito mode
4. Under administrator (minad) create app
   
5. Create user
6. Create org
7. Put user in the org with admin access
   
8. Create repos
   
9. Deploy Woodpecker

  woodpecker:
    image: woodpeckerci/woodpecker-server:v3.0.0-rc1-alpine
    volumes:
      - ./woodpecker:/var/lib/woodpecker/
    networks:
      - gtwp
    ports:
      - 8000:8000
    environment:
      - WOODPECKER_OPEN=true
      - WOODPECKER_ADMIN=minad
      - WOODPECKER_HOST=http://wp.local:8000
      - WOODPECKER_GITEA=true
      - WOODPECKER_GITEA_URL=http://gitea.local:3000
      - WOODPECKER_GITEA_CLIENT=5803cc8d-a1c4-40f3-a8a3-ef2fe14af9d9
      - WOODPECKER_GITEA_SECRET=gto_47lv2s253i4sxujw4cnljcpe75oyzhvqs3xfwnddyjwtmgwlntka
      - WOODPECKER_LOG_LEVEL=trace

10. Open Woodpecker in another Firefox tab
11. Login under administrator (minad) and activate repos
    
12. Open Chrome in Incognito mode
13. Login under user (harry) and see all (three) repos in the last visited block.
    

I didn't open a repository at all. I just logged in from another browser under another user.

Expected behavior

Under the second user (harry) the last visited repos block is empty.

System Info

WP 3.0.0-rc1, Gitea 1.22.6, Docker Desktop 4.35.1

Additional context

#4386 (comment)
#4386 (comment)

Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]