Evaluate pagination for protected_tags in repository settings
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=567528)
</details>
<!--IssueSummary end-->
### Problem
Repositories with many tags/branches experience slow loading times even after optimization changes.
### Proposed Solutions
1. **Pagination** - Break matching counts but improve load times
2. **Deferred loading** - Load tags/branches only when user interacts with UI
3. **UI optimization** - Review components using `tag_names`/`branch_names`
### Acceptance Criteria
* Implement pagination for tag/branch loading
* Add deferred loading to relevant UI components
* Measure performance with 5000+ tags
* Maintain good UX despite loading changes
**Related:** !200286
issue