Refactor annotation tool from WPF desktop app to .NET API

Replace the WPF desktop application (Azaion.Suite, Azaion.Annotator,
Azaion.Common, Azaion.Inference, Azaion.Loader, Azaion.LoaderUI,
Azaion.Dataset, Azaion.Test) with a standalone .NET Web API in src/.

Made-with: Cursor

.cursor/rules/coderule.mdc

@@ -0,0 +1,22 @@
+---
+description: Coding rules
+alwaysApply: true
+---
+# Coding preferences
+- Always prefer simple solution
+- Generate concise code
+- Do not put comments in the code
+- Do not put logs unless it is an exception, or was asked specifically
+- Do not put code annotations unless it was asked specifically 
+- Write code that takes into account the different environments: development, production
+- You are careful to make changes that are requested or you are confident the changes are well understood and related to the change being requested
+- Mocking data is needed only for tests, never mock data for dev or prod env
+- When you add new libraries or dependencies make sure you are using the same version of it as other parts of the code
+
+- Focus on the areas of code relevant to the task
+- Do not touch code that is unrelated to the task
+- Always think about what other methods and areas of code might be affected by the code changes
+- When you think you are done with changes, run tests and make sure they are not broken
+- Do not rename any databases or tables or table columns without confirmation. Avoid such renaming if possible.
+- Do not create diagrams unless I ask explicitly
+- Make sure we don't commit binaries, create and keep .gitignore up to date and delete binaries after you are done with the task

.cursor/rules/techstackrule.mdc

@@ -0,0 +1,9 @@
+---
+description: Techstack
+alwaysApply: true
+---
+# Tech Stack
+- Using Postgres database
+- Depending on task, for backend prefer .Net or Python. Could be RUST for more specific things.
+- For Frontend, use React with Tailwind css (or even plain css, if it is a simple project)
+- document api with OpenAPI