refactor: centralize service configs in config/services/ directory

Addresses issue #11 - prevent root directory clutter with service configs

Changes:
- Move homeassistant/ → config/services/homeassistant/
- Move cryptpad/ → config/services/cryptpad/
- Move reverseproxy/ → config/services/reverseproxy/
- Update Docker Compose volume mounts to reference new paths
- All tests pass, maintaining full functionality

Benefits:
- Cleaner root directory structure
- Logical grouping of service-specific configurations
- Follows established config/ directory pattern
- Scalable for future service additions

No new functionality added - pure reorganization following TDD red/green/refactor approach.

Author: chutch3

cryptpad/config.js config/services/cryptpad/config.jscryptpad/config.js renamed to config/services/cryptpad/config.js

@@ -89,7 +89,7 @@ module.exports = {
 
     /*  httpSafePort purpose is to emulate another origin for the sandbox when
      *  you don't have two domains at hand (i.e. when httpSafeOrigin not defined).
-     *  It is meant to be used only in case where you are working on a local 
+     *  It is meant to be used only in case where you are working on a local
      *  development instance. The default value is your httpPort + 1.
      *
      */

homeassistant/configuration.yaml …ervices/homeassistant/configuration.yamlhomeassistant/configuration.yaml renamed to config/services/homeassistant/configuration.yaml homeassistant/configuration.yaml renamed to config/services/homeassistant/configuration.yaml

@@ -6,4 +6,4 @@
 <h1>Backend not found</h1>
 <p>The backend you requested was not found. Please check the URL and try again.</p>
 </body>
-</html>
+</html>