Fixed Issues identified in HASHIQUBE_ISSUES.md

[ruaan-deysel]

This pull request introduces significant updates across multiple areas of the HashiQube project, focusing on improving security, usability, compatibility, and documentation. The most notable changes include enhanced security measures, better error handling and resilience, improved data persistence, and expanded platform compatibility. Additionally, the documentation has been extensively updated to provide clearer guidance and support for users.

Security Enhancements:

• Replaced hardcoded SSH keys in the Dockerfile with dynamically generated unique keys for the vagrant user, ensuring better security during provisioning. The private key is stored securely for provisioning purposes.
• Updated credential management practices, including storing Vault root credentials in a secure location and using temporary tokens with limited TTL and policies.

Usability and Resilience:

• Added a standardized error handling library (hashiqube/error_handling.sh) with features like consistent logging, retry mechanisms, and service availability checks.
• Created a health check script (hashiqube/health_check.sh) for service monitoring with color-coded outputs for better issue identification.

Compatibility and Configuration:

• Introduced architecture and platform detection scripts to support x86_64, ARM64, ARM32, and i386 architectures, along with platform-specific guidance in COMPATIBILITY.md.
• Added a centralized configuration system (hashiqube/config.sh) for managing environment-specific settings and secure storage of sensitive values.

Documentation Improvements:

• Created new documentation files, including COMPATIBILITY.md for platform compatibility, DEPENDENCIES.md for component dependencies, and updated the README.md with references to new tools and features. [1] [2] [3]
• Added a DEFAULT_CREDENTIALS.md file to clarify default credentials and emphasize the need to change them in production environments.

Data Persistence:

• Replaced temporary file system mounts with named Docker volumes in docker-compose.yml for persistent storage, ensuring data survives container restarts and rebuilds.