feat(build): migrate from Prettier to Oxfmt for performant code formatting (#42434)

docs/user_docs_versioned_docs/version-6.0.0/contributing/development.mdx

@@ -3,6 +3,7 @@ title: Setting up a Development Environment
 sidebar_position: 3
 version: 1
 ---
+
 # Setting up a Development Environment
 
 The documentation in this section is a bit of a patchwork of knowledge representing the
@@ -123,6 +124,7 @@ docker-compose up
 ## GitHub Codespaces (Cloud Development)
 
 GitHub Codespaces provides a complete, pre-configured development environment in the cloud. This is ideal for:
+
 - Quick contributions without local setup
 - Consistent development environments across team members
 - Working from devices that can't run Docker locally
@@ -269,17 +271,21 @@ You can also run the pre-commit checks manually in various ways:
 ## Working with LLMs
 
 ### Environment Setup
+
 Ensure Docker Compose is running before starting LLM sessions:
+
 ```bash
 docker compose up
 ```
 
 Validate your environment:
+
 ```bash
 curl -f http://localhost:8088/health && echo "✅ Superset ready"
 ```
 
 ### LLM Session Best Practices
+
 - Always validate environment setup first using the health checks above
 - Use focused validation commands: `pre-commit run` (not `--all-files`)
 - **Read [LLMS.md](https://github.com/apache/superset/blob/master/LLMS.md) first** - Contains comprehensive development guidelines, coding standards, and critical refactor information
@@ -291,6 +297,7 @@ curl -f http://localhost:8088/health && echo "✅ Superset ready"
 - Follow the TypeScript migration guidelines and avoid deprecated patterns listed in LLMS.md
 
 ### Key Development Commands
+
 ```bash
 # Frontend development
 cd superset-frontend
@@ -591,7 +598,7 @@ If you want to use the same flag in the client code, also add it to the FeatureF
 
 ```typescript
 export enum FeatureFlag {
-  SCOPED_FILTER = "SCOPED_FILTER",
+  SCOPED_FILTER = 'SCOPED_FILTER',
 }
 ```
 
@@ -884,9 +891,9 @@ VSCode will not stop on breakpoints right away. We've attached to PID 6 however
 To debug Flask running in POD inside a kubernetes cluster, you'll need to make sure the pod runs as root and is granted the SYS_TRACE capability.These settings should not be used in production environments.
 
 ```yaml
-  securityContext:
-    capabilities:
-      add: ["SYS_PTRACE"]
+securityContext:
+  capabilities:
+    add: ['SYS_PTRACE']
 ```
 
 See [set capabilities for a container](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-capabilities-for-a-container) for more details.