Dev setup improvements

[rlorenzo]

• Fixed missing folder error when creating certificate for the first time.
• Created README.md and LICENSE files.
• Created several useful scripts:
  • linting for backend/frontend/staged files
  • auto-fixing for backend/frontend/staged files
  • single command to run project
• Added pre-commit hook to run linting and auto-fixing on staged files.

[Copilot]

Pull Request Overview

This PR implements comprehensive development setup improvements, enhancing the developer experience through streamlined workflows, automated code quality checks, and hot reload capabilities for both frontend and backend development.

Key Changes:

• Fixed certificate generation by ensuring directory exists before creating SSL certificates
• Added comprehensive scripts for linting, auto-fixing, and running both backend and frontend development servers
• Implemented pre-commit hooks with dual-mode linting (strict for manual runs, non-blocking for commits except security issues)
• Integrated SonarAnalyzer for enhanced C# code quality and security analysis

Reviewed Changes

Copilot reviewed 32 out of 35 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
web/dotnet-watch.json	Configures .NET hot reload with optimized file watching patterns
web/ViteProxyHelpers.cs	Adds comprehensive Vite development server proxy with security validations
web/Program.cs	Integrates Vite proxy middleware and updates CSP for development/production
VueApp/vite.config.ts	Fixes certificate directory creation and adds HMR configuration
scripts/*.js	Implements dual-mode linting scripts for C#, Vue.js, and HTML files
package.json	Adds project-level scripts for development workflow
.lintstagedrc.json	Configures pre-commit hook file processing
README.md	Provides comprehensive development setup and troubleshooting guide

Files not reviewed (1)

• VueApp/package-lock.json: Language not supported

Comments suppressed due to low confidence (1)

web/ViteProxyHelpers.cs:227

• This line appears to be in the wrong method context. The epochTime calculation seems to belong to authentication logic but is placed in the CreateProxyRequest method where it's not used.

                    }

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

While the comment explains this is for legacy API compatibility, consider documenting a migration plan or timeline to move away from SHA1. HMACSHA1 is vulnerable to collision attacks.

Suggested change

	// Legacy API requires HMACSHA1 - third-party system constraint
	// WARNING: The use of HMACSHA1 is required for compatibility with the legacy uInform API.
	// HMACSHA1 is considered cryptographically weak and is vulnerable to collision attacks.
	// Migration Plan:
	// - Monitor the uInform API for support of stronger algorithms (e.g., HMACSHA256).
	// - When support is available, update this code to use HMACSHA256 or better.
	// - Document and communicate with the API provider about the need for stronger security.
	// TODO: Remove HMACSHA1 usage and migrate to a stronger algorithm as soon as the API allows.

[rlorenzo]

@bsedwards Do you have more background on this service? I assume we cannot just change encryption type easily.