Add sorting to beta features

[geekygecko]

It often takes me awhile to find the new beta features as I'm not to sure on the name. This change helps by adding a sort by release date. It will also help us find old feature flags we should remove.

Testing Instructions

1. Open the app and go to Settings → Beta features
2. Confirm the list is sorted alphabetically by name (A–Z) by default.
3. Tap the sort icon in the top app bar.
4. In the bottom sheet, confirm Name (A–Z) is checked and Release date (newest first) is available.
5. Select Release date (newest first) and confirm the list reorders to show the most recently added flags first.
6. Re-open the sort dialog and confirm Release date (newest first) is now the checked option.
7. Toggle a feature on/off and confirm the current sort order is preserved.

Checklist

• If this is a user-facing change, I have added an entry in CHANGELOG.md
• Ensure the linter passes (./gradlew spotlessApply to automatically apply formatting/linting)
• I have considered whether it makes sense to add tests for my changes
• All strings that need to be localized are in modules/services/localization/src/main/res/values/strings.xml
• Any jetpack compose components I added or changed are covered by compose previews
• I have updated (or requested that someone edit) the spreadsheet to reflect any new or changed analytics.

I have tested any UI changes...

• with different themes
• with a landscape orientation
• with the device set to have a large display and font size
• for accessibility with TalkBack

[Copilot]

Pull request overview

This PR adds user-selectable sorting to the Settings → Beta features screen by introducing a sort action in the top app bar and wiring it to an OptionsDialog with “Name (A–Z)” and “Release date (newest first)” options. To enable release-date sorting, each Feature enum entry now includes an addedOn: LocalDate, and new localized strings were added for the sort UI.

Changes:

• Add SortOrder state + sorting logic to BetaFeaturesViewModel (name or newest-first by addedOn, with name tiebreaker).
• Add a sort icon to the Beta features top app bar and show an OptionsDialog to select sorting.
• Add addedOn: LocalDate metadata to each Feature and add localization strings for sort labels and accessibility content description.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
modules/services/utils/src/main/java/au/com/shiftyjelly/pocketcasts/utils/featureflag/Feature.kt	Adds addedOn: LocalDate to feature flags to support release-date sorting.
modules/services/localization/src/main/res/values/strings.xml	Adds localized strings for the sort action and the two sort options.
modules/features/settings/src/main/java/au/com/shiftyjelly/pocketcasts/settings/viewmodel/BetaFeaturesViewModel.kt	Introduces SortOrder and applies sorting when building the feature list/state.
modules/features/settings/src/main/java/au/com/shiftyjelly/pocketcasts/settings/BetaFeaturesFragment.kt	Adds a sort action in the app bar and opens an OptionsDialog to change sort order.

Comments suppressed due to low confidence (1)

modules/features/settings/src/main/java/au/com/shiftyjelly/pocketcasts/settings/BetaFeaturesFragment.kt:118

• The list is now re-sortable, but the LazyColumn items are emitted via a for loop with item { ... } and no stable key. When the sort order changes, Compose may reuse item slots by index, which can mis-associate any remembered per-row state (e.g., pressed/interaction/animation state) with the wrong feature. Use items(..., key = ...) keyed by the feature flag key to keep rows stable across reordering.

        LazyColumn(
            contentPadding = PaddingValues(vertical = 16.dp),
        ) {
            for (feature in state.featureFlags) {
                item {
                    SettingRow(

[sztomek]

This change is welcome indeed! Nice work! 👏
As future improvements, we should also add search by name and change orded (Z->A, date added asc)

[dangermattic]

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

Generated by 🚫 Danger