Refactor provider composition and ESLint configuration

- Add new provider composition system with validation
- Create providerComposition.tsx for centralized provider management
- Implement providerOrderValidator.tsx to ensure correct provider order
- Add comprehensive tests for provider composition
- Create custom ESLint rules in frontend/eslint-rules/
- Update ESLint configuration
- Update architecture and tasks documentation

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

frontend/eslint.config.ts

@@ -3,9 +3,10 @@ import tseslint from "typescript-eslint";
 import reactHooks from "eslint-plugin-react-hooks";
 import reactPlugin from "eslint-plugin-react";
 import prettierConfig from "eslint-config-prettier";
+import bangguiRulesModule from "./eslint-rules/index.js";
 
 export default tseslint.config(
-  { ignores: ["dist", "eslint.config.ts", ".vite"] },
+  { ignores: ["dist", "eslint.config.ts", ".vite", "eslint-rules"] },
   {
     extends: [js.configs.recommended, ...tseslint.configs.strictTypeChecked],
     files: ["**/*.{ts,tsx}"],
@@ -18,6 +19,7 @@ export default tseslint.config(
     plugins: {
       react: reactPlugin,
       "react-hooks": reactHooks,
+      bangui: bangguiRulesModule,
     },
     settings: {
       react: {
@@ -34,6 +36,7 @@ export default tseslint.config(
       "@typescript-eslint/no-explicit-any": "error",
       "@typescript-eslint/explicit-function-return-type": "warn",
       "@typescript-eslint/no-unused-vars": ["error", { argsIgnorePattern: "^_", varsIgnorePattern: "^_" }],
+      "bangui/provider-order": "warn",
     },
   },
   prettierConfig,