Add config setting for default repository view

[Copilot]

Adds configurable default repository view setting at both server and user levels with comprehensive test coverage.

Implementation Summary

Key Components:

• RepositoryDefaultView enum with Detail, Tree, Commits, Tags options
• Server-level default setting (global for all users)
• User-level override setting (with "Use Server Default" option)
• Updated navigation in repository list and dropdown to respect settings
• Database migrations for both SQLite and SQL Server

Resolution Order:
User Setting → Server Setting → Detail (fallback)

The feature allows administrators to set a site-wide default view, while individual users can customize their own preference or inherit the server default.

How It Works

• For Administrators: Navigate to Server → Settings and select the default repository view for all users
• For Users: Navigate to Account → Settings and either select a personal preference or use the server default
• When navigating: Clicking on repository names now directs users to their configured preferred view

Test Coverage

Added comprehensive test suite with 29 new tests (all passing):

• RepositoryViewHelperTests (5 tests): Validates action name mapping for each view type
• ServerSettingsServiceTests (6 tests): Tests server settings persistence, retrieval, defaults, and caching
• UserSettingsServiceTests (9 tests): Tests user settings persistence, null handling, multi-user scenarios, and cache behavior
• RepositoryDefaultViewTests (9 tests): Validates enum values, Display attributes, and resource bindings

Total test suite: 266 tests passing

Fixes #46

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add config setting for default repository view</issue_title>
<issue_description>Sometimes I would like this.</issue_description>

<agent_instructions>Before changing code, provide a described solution and ask for confirmation.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@Matt-17 There should be a setting in Server/Settings and User/Settings.

Fixes #46

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Matt-17]

@copilot This sounds like a great plan. Execute it!

[Copilot]

@copilot This sounds like a great plan. Execute it!

Done! I've implemented the default repository view configuration feature with the following changes:

Commit: 57c3f47

What was added:

1. RepositoryDefaultView enum - Supports Detail, Tree, Commits, and Tags views
2. Server Settings - Global default repository view configuration (defaults to Detail)
3. User Settings - User-specific override with "Use Server Default" option
4. Navigation Updates - Repository links now respect user/server preferences
5. Database Migrations - Created for both SQLite and SQL Server

How it works:

• Administrators can set a global default view in Server → Settings
• Users can override this in Account → Settings (or use server default)
• When users click on repository names, they navigate to their configured preferred view
• Resolution order: User Setting → Server Setting → Detail (fallback)

The new dropdown appears in both Server Settings and User Settings views, allowing selection between Detail, Browse (Tree), Commits, and Tags views.

[Matt-17]

@copilot Fine. Add some tests!

[Copilot]

@copilot Fine. Add some tests!

Added comprehensive test suite with 29 tests covering all aspects of the default repository view feature.

Commit: fe3468f

Test Coverage:

• RepositoryViewHelperTests (5 tests) - Validates action name mapping for Detail, Tree, Commits, Tags, and invalid values
• ServerSettingsServiceTests (6 tests) - Tests server settings persistence, retrieval, defaults, updates, and caching
• UserSettingsServiceTests (9 tests) - Tests user settings with null handling, multi-user scenarios, server default fallback, and cache behavior
• RepositoryDefaultViewTests (9 tests) - Validates enum values, Display attributes, and resource string bindings

All 29 new tests pass. Total test suite: 266 tests passing.