Fix loading performance for pages with many links caused by excessive re-computation

[mportiz08]

Bug/issue #, if applicable: 136247329 (#894)

Summary

This fixes a performance regression (#894) when loading pages with many links that was introduced with #878.

The problem is that any logic in the referencesProvider mixin does not get cached once for each client as I mistakenly assumed, so every component using this mixin was unintentionally re-running the logic for inactivating known external links, which becomes noticeable when there is a big list of references.

To fix it, I moved this logic to the setReferences methods in the appropriate stores, and I'm making sure to update the refs and re-run this logic whenever the global includedArchiveIdentifiers data changes.

(I closed #898 which was a less ideal solution to this same issue—thanks for pointing out the root issue that I missed @hqhhuang!)

Testing

Describe how a reviewer can test the functionality of your PR. Provide test content to test with if
applicable.

Steps:

1. Follow and verify the testing instructions for the original PR in Inactivate known external links #878.
2. Verify that the performance issue from Slow rendering of root-level pages #894 is now also resolved.

Checklist

Make sure you check off the following items. If they cannot be completed, provide a reason.

• Added tests
• Ran npm test, and it succeeded
• Updated documentation if necessary

[mportiz08]

@swift-ci test

[mportiz08]

@hqhhuang I removed the update logic from non-documentation-page components as we discussed offline since it's not technically necessary there yet.

[mportiz08]

@swift-ci test

[mportiz08]

@swift-ci test

[heckj]

Is this PR included in the content that's exposed with swift 6.0.2 (toolchain with Xcode 16.1), or is it coming in a future version of the swift toolchain (6.1?) (was it cherry picked?)

[mportiz08]

Is this PR included in the content that's exposed with swift 6.0.2 (toolchain with Xcode 16.1), or is it coming in a future version of the swift toolchain (6.1?) (was it cherry picked?)

I believe it is only on the latest development Swift toolchain at the moment.

If you need a workaround using an existing toolchain, you can clone the latest version of swift-docc-render-artifact and set DOCC_HTML_DIR=/path/to/swift-docc-render-artifact/dist as part of a docc command invocation to use the latest version of the renderer that includes this fix.