[DREAM-803] Migrate wiki, OAuth and project settings lists to BorderBoxList

[myabc]

Ticket

https://community.openproject.org/wp/DREAM-803

What are you trying to accomplish?

Third slice of the DREAM-697 split: mechanical consumer migrations from Primer::Beta::BorderBox / border_box_container to OpenProject::Common::BorderBoxListComponent, one commit per surface.

• Wikis::CollapsiblePageLinksComponent and Wikis::RelationPageLinksComponent
• Portfolios::IndexComponent
• OAuth::Applications::IndexComponent
• Projects::Settings::LifeCycle::IndexComponent
• Projects::Settings::ProjectCustomFieldSections::ShowComponent and its CreationWizard twin
• My::Notifications::ShowPageComponent

The life cycle and project custom-field sections lists opt into empty_state_behavior: :dynamic: filtering to no matches shows the blankslate inside each box, replacing the life cycle page's detached plain-text "No items found" notice.

What approach did you choose and why?

Each migration is a focused vertical slice with its component spec, so surfaces can be reviewed independently and reverted individually if needed. Stacked on #24644 only for linear review order; it does not depend on those surfaces.

Visual comparisons

Show baseline/candidate screenshots

Baseline is shown on the left; the candidate stack is shown on the right. (Screenshots predate the empty-state rework; regeneration pending.)

Work package wiki tab

Portfolios

OAuth applications

Project life cycle

Project custom-field sections

Project creation wizard attributes

My notifications

Merge checklist

• Added/updated tests
• Added/updated documentation in Lookbook (patterns, previews, etc)
• Tested major browsers (Chrome, Firefox, Edge, ...)

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 20 out of 20 changed files in this pull request and generated no new comments.

Suppressed comments (3)

app/components/projects/settings/project_custom_field_sections/show_component.html.erb:10

• Argument indentation is inconsistent: test_selector: is over-indented relative to the other keyword arguments in this BorderBoxListComponent.new call. This diverges from existing BorderBoxListComponent usages and can trigger ERB/Ruby linting alignment cops.

      OpenProject::Common::BorderBoxListComponent.new(
        container: "project-custom-field-section-#{@project_custom_field_section.id}",
        position: :relative,
        mb: 3,
        classes: "op-project-custom-field-section",
                test_selector: "project-custom-field-section-#{@project_custom_field_section.id}"
      )

app/components/projects/settings/creation_wizard/project_custom_field_sections/show_component.html.erb:10

• Argument indentation is inconsistent: test_selector: is over-indented relative to the other keyword arguments in this BorderBoxListComponent.new call. Aligning the keyword arguments matches existing component usages and avoids potential lint failures.

      OpenProject::Common::BorderBoxListComponent.new(
        container: "project-custom-field-section-#{@project_custom_field_section.id}",
        position: :relative,
        mb: 3,
        classes: "op-project-custom-field-section",
                test_selector: "project-custom-field-section-#{@project_custom_field_section.id}"
      )

app/components/projects/settings/life_cycle/index_component.html.erb:31

• test_selector: is mis-indented in the BorderBoxListComponent.new argument list, which is inconsistent with surrounding keyword alignment and may fail ERB/Ruby alignment linting.

        OpenProject::Common::BorderBoxListComponent.new(
          container: "project-life-cycle-administration",
          position: :relative,
          mb: 3,
                    test_selector: "project-life-cycle-administration"
        )

[github-actions]

Warning

Flaky specs

• rspec ./modules/wikis/spec/features/admin/internal_provider_spec.rb[1: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 #24645, linked for reference only):

- `rspec ./modules/wikis/spec/features/admin/internal_provider_spec.rb[1:1]`

Treat this as a standalone task, unrelated to PR #24645. Create a new branch from origin/dev and open a new pull request targeting dev — do not stack it on PR #24645 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 @myabc 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 @myabc, and request a review from @myabc.
On every commit, set @myabc 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.

[bsatarnejad]

LGTM 👍🏼