Implement edit and delete operations for custom menu entries (US2)

[Copilot]

Description

What's new?

Adds full CRUD capabilities to custom menu entries feature. User Story 1 (create/list) was complete; this implements User Story 2 (edit/delete).

Backend changes:

• PUT /api/menu-entries/{id} - Updates entry with validation (name uniqueness excluding self, URL format, 100 char limit)
• DELETE /api/menu-entries/{id} - Hard deletes entry after existence check
• Both endpoints require menuentry:write authorization
• Returns proper status codes: 200 OK (update), 204 No Content (delete), 404 (not found), 400 (validation), 409 (duplicate)

Frontend changes:

• Edit button opens pre-filled dialog with real-time validation and external/internal URL indicator
• Delete button shows confirmation dialog before permanent removal
• List refreshes automatically after operations
• NavMenu handles deleted entries gracefully

Test coverage:

• Service layer: update/delete with validation scenarios (duplicates, invalid URLs, missing entries)
• Controller layer: PUT/DELETE endpoints with authorization and error responses
• Client service layer: HTTP client wrapper tests for all operations
• All 1610 tests passing (100% pass rate)
• Fixed HTTP content type assertions in MenuEntryClientService tests to match PostAsJsonAsync/PutAsJsonAsync/PatchAsJsonAsync implementation
• Added IMenuEntryClientService mock to NavMenu and MainLayout test fixtures to support component rendering

Validation enforced:

• Name: required, max 100 chars, unique (excluding self on update)
• URL: required, valid HTTP/HTTPS or relative path
• ID matching between URL parameter and request body
• Entity existence before update/delete

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Tests
• Other

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Feature: Creation of custom menu entries</issue_title>
<issue_description>Is your feature request related to a problem? Please describe.
It could be nice to be able to add custom menu entries, either with quick links to specific internal resources, or resources external to the portal (monitoring solution, documentation, ticketing site, ...)

Describe the solution you'd like
Make it possible to create the aforementioned menu entries from the UI (with RBAC when implemented) and from the API. The links would be in a separate section. We should be able to decide the order of the menu entries in this section, and also where to put this section (first, last, somewhere between existing menu entries...)

Describe alternatives you've considered
N/A

Additional context
We have a lot of web resources linked to our IoT solution on-site and we would like to make it easier for our user to navigate to them if they don't have all the links</issue_description>

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

Custom agent used: speckit.specify
Create or update the feature specification from a natural language feature description.

• Fixes Feature: Creation of custom menu entries #2957

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-advanced-security]

CodeQL found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

[kbeaugrand]

@copilot fix unit tests

[Copilot]

@copilot fix unit tests

Fixed in commit e315ced. All 29 MenuEntry tests now passing (was 26/29).

The issue was incorrect HTTP content type assertions - tests expected StringContent but PostAsJsonAsync/PutAsJsonAsync/PatchAsJsonAsync create ObjectContent<T> or JsonContent. Updated to match patterns used in other client service tests.

[kbeaugrand]

@copilot some tests still failed

[Copilot]

@copilot some tests still failed

Fixed in commit 8ea8478. All 1610 tests now passing (was 1577/1610).

The issue was that NavMenu and MainLayout tests were missing the IMenuEntryClientService mock. When NavMenu was updated to load custom menu entries, it injected this service, but the test fixtures didn't register it. Added mock setup to both NavMenuTests and MainLayoutTests following the same pattern used for other client services in the codebase.

[codecov]

Codecov Report

❌ Patch coverage is 33.81443% with 321 lines in your changes missing coverage. Please review.
✅ Project coverage is 79.83%. Comparing base (d991cb6) to head (67ebf97).

Files with missing lines	Patch %	Lines
...l.Client/Pages/MenuEntries/MenuEntryListPage.razor	0.00%	85 Missing ⚠️
...ient/Dialogs/MenuEntries/EditMenuEntryDialog.razor	0.00%	79 Missing ⚠️
...nt/Dialogs/MenuEntries/CreateMenuEntryDialog.razor	0.00%	68 Missing ⚠️
...l.Server/Controllers/v1.0/MenuEntriesController.cs	58.44%	30 Missing and 2 partials ⚠️
...Portal.Infrastructure/Services/MenuEntryService.cs	72.04%	20 Missing and 6 partials ⚠️
src/IoTHub.Portal.Client/Shared/NavMenu.razor	33.33%	13 Missing and 1 partial ⚠️
...Infrastructure/Repositories/MenuEntryRepository.cs	0.00%	7 Missing ⚠️
...Hub.Portal.Client/Dialogs/DeleteConfirmation.razor	0.00%	6 Missing ⚠️
...b.Portal.Client/Services/MenuEntryClientService.cs	92.59%	0 Missing and 2 partials ⚠️
...b.Portal.Shared/Extensions/PermissionsExtension.cs	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3308      +/-   ##
==========================================
- Coverage   81.38%   79.83%   -1.56%     
==========================================
  Files         376      387      +11     
  Lines       14360    14845     +485     
  Branches     1224     1282      +58     
==========================================
+ Hits        11687    11851     +164     
- Misses       2295     2605     +310     
- Partials      378      389      +11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.