Fix Microsoft Clarity consent API property names for GDPR compliance (#786)

Fixes critical Microsoft Clarity consent implementation to ensure
compliance with GDPR requirements ahead of the October 31, 2025
enforcement deadline.

## Problem

The Microsoft Clarity consent API call was using incorrect property
names, preventing proper consent signal transmission:

```javascript
// ❌ Incorrect - using camelCase
clarity('consentv2', {
    ad_Storage: this.consentState.ad_storage,
    analytics_Storage: this.consentState.analytics_storage
});
```

This meant that user consent preferences were not being properly
communicated to Microsoft Clarity, potentially causing compliance issues
for users in EEA, UK, and Switzerland regions.

## Solution

Updated the consent API call to use the correct property names as
specified in Microsoft's documentation:

```javascript
// ✅ Correct - using lowercase with underscores
clarity('consentv2', {
    ad_storage: this.consentState.ad_storage,
    analytics_storage: this.consentState.analytics_storage
});
```

## Testing

Added comprehensive testing tools including Microsoft's recommended
verification function:

```javascript
// Microsoft's official verification function
clarity('metadata', (d, upgrade, consent) => {
    console.log('consentStatus:', consent);
}, false, true, true);
```

The implementation now correctly shows:
- **Consent DENIED**: `{analytics_storage: "DENIED", ad_storage:
"DENIED"}`
- **Consent GRANTED**: `{analytics_storage: "GRANTED", ad_storage:
"GRANTED"}`

## Screenshot

![Consent Verification Test
Results](https://github.com/user-attachments/assets/321326c8-f7bf-4997-8ef9-3aa142a95a0c)

The test page demonstrates successful consent state management with
proper API integration.

## Impact

- ✅ **Compliance**: Site now properly implements Microsoft Clarity
consent mode
- ✅ **Privacy**: User consent preferences are correctly respected
- ✅ **Functionality**: Clarity tracking works as expected based on
consent state
- ✅ **Future-proof**: Ready for October 2025 enforcement requirements

This minimal but critical fix ensures that essentialcsharp.com maintains
proper user privacy controls while enabling full Microsoft Clarity
functionality when consent is granted.

<!-- START COPILOT CODING AGENT TIPS -->
---

✨ Let Copilot coding agent [set things up for
you](https://github.com/IntelliTect/EssentialCSharp.Web/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot)
— coding agent works faster and does higher quality work when set up for
your repo.

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: BenjaminMichaelis <[email protected]>
Co-authored-by: Benjamin Michaelis <[email protected]>

Author: Copilot

EssentialCSharp.Web/wwwroot/js/consent-manager.js

@@ -312,8 +312,8 @@ class ConsentManager {
         if (window.clarity) {
             try {
                 clarity('consentv2', {
-                    ad_Storage: this.consentState.ad_storage,
-                    analytics_Storage: this.consentState.analytics_storage
+                    ad_storage: this.consentState.ad_storage,
+                    analytics_storage: this.consentState.analytics_storage
                 });
             } catch (error) {
                 console.warn('Failed to update Clarity consent:', error);