feat: enforce prefix for persisted route query values

[kulmann]

Description

Pagination for admin-settings has been introduced recently. A weird-ish url query was used for the items per page: admin-settings-items-per-page. With this PR I'm streamlining that to be items-per-page in both the admin-settings and files apps respectively by enforcing a prefix for persisting the query value into the localStorage. A kind of prefix already existed before: it was named routeName, which is too specific, so I renamed it. As a result the items per page in the files app will be persisted into oc-options_files_items-per-page and the items per page in the admin-settings app will be persisted into oc-options_admin-settings_items-per-page.

Motivation and Context

Consistency in a) localStorage, b) url query and c) developer experience

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

Open tasks:

• changelog item
• fix unit tests

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

77.3% Coverage
0.0% Duplication