Add migration to fix zero forge_id in orgs table

[xoxys]

Fixes: #4918

• drive-by fix that unifies the migration file names
• add migration for forge_id=0 in orgs table

I have not worked much with XORM and even less with the migrations, so please let me know if this is wrong.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 26.26%. Comparing base (a3cc61b) to head (3287f35).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4924      +/-   ##
==========================================
+ Coverage   26.25%   26.26%   +0.01%     
==========================================
  Files         399      400       +1     
  Lines       28397    28401       +4     
==========================================
+ Hits         7456     7460       +4     
  Misses      20268    20268              
  Partials      673      673              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[lafriks]

Code looks good but what is the source of such records being created?

[qwerty287]

I think the problem was that when we added the forge_id column we didn't set a default value so on all old records it was set to 0.

[xoxys]

Do we missed the "orgs" table migration in https://github.com/woodpecker-ci/woodpecker/blob/main/server/store/datastore/migration/008_set_default_forge_id.go then?