[OP-19930] Fix lost seeded custom styles when seeding multiple

[oliverguenther]

We suspect something is being discarded without proper logging in the seed design background job. Adds more error logging and retrying for HTTP errors

https://community.openproject.org/work_packages/OP-19930

[oliverguenther]

Thanks @NobodysNightmare , I changed the order and while doing more tests on the newly deployed cluster, I found the underlying issue:

CarrierWave only uploads in an after_commit commit, and with the change to the job, we save the CustomStyle multiple times in a background job. Rails runs only ONE callback of these saves (the last one), so while the DB looks like all files were uploaded, only one of the files are being updated. I think we just tested with one file locally, so this was not found before 🫠

[github-actions]

Warning

Flaky specs

• rspec ./spec/features/activities/work_package/activities_spec.rb[1:5:2:1]
• rspec ./spec/features/projects/lists/filters_spec.rb[1:6:1]

🤖 Ask Copilot to investigate

Copy the prompt below into a new comment on this PR to delegate the investigation to GitHub Copilot. It will look into the flakiness and open a separate pull request with you as reviewer.

@copilot The following spec(s) are flaky in CI (first seen on PR #24713, linked for reference only):

- `rspec ./spec/features/activities/work_package/activities_spec.rb[1:5:2:1]`
- `rspec ./spec/features/projects/lists/filters_spec.rb[1:6:1]`

Treat this as a standalone task, unrelated to PR #24713. Create a new branch from origin/dev and open a new pull request targeting dev — do not stack it on PR #24713 or reuse that branch.

Follow the playbook in docs/development/testing/handling-flaky-tests/README.md to find the root cause and fix the underlying race — do not skip, delete, or weaken the spec to make it pass; disabling is a last resort per the playbook, and only with a bug ticket. Verify the fix by running the spec(s) repeatedly (e.g. `script/bulk_run_rspec --run-count 10`).

If you cannot reproduce the flake or are not confident in a fix after reasonable investigation, do not fabricate a change or skip the spec to force CI green. Instead, leave the pull request in draft and document what you tried, the suspected cause, and any leads in its description, then assign @oliverguenther to take over.

Once the fix is verified, title the PR after the spec(s) it fixes, and use the PR description to explain the root cause, how the change resolves it, and the before/after results. Label the PR `flaky-spec`, assign @oliverguenther, and request a review from @oliverguenther.
On every commit, set @oliverguenther as the sole co-author with a `Co-authored-by:` trailer (use their GitHub no-reply email so it links to their account), so it is traceable who dispatched the fix.

[NobodysNightmare]

LGTM, thanks for the detailed explanations