Reader: Update when the results controller is reset for tags feed

[wargcm]

Description

Fixes selecting a filter on the "Your Tags" feed. There was a race condition with recreating the results controller which caused unexpected behavior. This moves the recreation of that controller to when the setContent is called.

Testing

To test:

• Launch Jetpack and login
• Navigate to the "Your Tags" feed
• Scroll the feed down
• Tap on the tags filter chip
• Select a tag to filter
• 🔎 Verify the feed is properly filtered and scrolls to the top
• Scroll down on the filtered feed
• Tap on the X to remove the filter
• 🔎 Verify the filter is removed, the tags feed displays again, and it starts at the top of the feed

Regression Notes

1. Potential unintended areas of impact
   Subscriptions feed filtering

2. What I did to test those areas of impact (or what existing automated tests I relied on)
   Manual testing

3. What automated tests I added (or what prevented me from doing so)
   N/A
   PR submission checklist:

• I have completed the Regression Notes.
• I have considered adding unit tests for my changes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Testing checklist:

• WordPress.com sites and self-hosted Jetpack sites.
• Portrait and landscape orientations.
• Light and dark modes.
• Fonts: Larger, smaller and bold text.
• High contrast.
• VoiceOver.
• Languages with large words or with letters/accents not frequently used in English.
• Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)
• iPhone and iPad.
• Multi-tasking: Split view and Slide over. (iPad)

[dangermattic]

	1 Warning
⚠️	This PR is assigned to the milestone 24.9. This milestone is due in less than 4 days. Please make sure to get it merged by then or assign it to a milestone with a later deadline.

Generated by 🚫 Danger

[wargcm]

I had to use scrollToRow here because using setContentOffset would scroll too high sometimes above the first card. I believe this was due to the pull-to-refresh.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.

	App Name	WordPress Alpha
	Configuration	Release-Alpha
	Build Number	pr23179-0bafe68
	Version	24.8
	Bundle ID	org.wordpress.alpha
	Commit	0bafe68
	App Center Build	WPiOS - One-Offs #9860

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.

	App Name	Jetpack Alpha
	Configuration	Release-Alpha
	Build Number	pr23179-0bafe68
	Version	24.8
	Bundle ID	com.jetpack.alpha
	Commit	0bafe68
	App Center Build	jetpack-installable-builds #8908

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

[dvdchr]

I've tested and verified that the race condition no longer happens in the 'Your Tags' stream. I've also tested this with a self-hosted site without Jetpack connection (where the issue was happening more often before this fix.)

Looking good!