Add credential & udiskie support, extend API, add helpers, and update config

[gmmcosta15]

Description

Select the type:

• Feature
• Bug fix
• Code refactor
• Documentation

files.py:

• Add credential section handling for specifying usernames.
• Add udiskie section config handling for defining automount paths.
• Create symlink in ~/home/printer_data/USB/ mapping the username to its udiskie automount path.
• Ensure symlink is recreated when the user clicks the printer button.

moonrakerComm.py:

• Add JSON‑RPC API methods to support future implementations.

moonrest.py:

• Add HTTP endpoints for interacting with Moonraker.
• Add ability to send files using the _post request method.

helper_methods.py:

• Add method to check if a process is running.
• Add method to calculate the SHA‑256 hash of a file.

logger.py:

• Automatically create logs directory if it does not already exist

BlocksScreen.cfg:

• Add the two new configuration sections, credential and udiskie.

Motivation

• User credential and automount support - Previously, there was no standardized way for users to define their username or specify USB automount paths. Adding credential and udiskie sections in the configuration improves usability and lets users tailor the system to their environment.
• Reliable symlink creation - A symlink in ~/home/printer_data/USB now consistently maps the configured username to the appropriate udiskie automount path. The implementation ensures this symlink is created and recreated when necessary (e.g., when the user clicks the printer button), enhancing consistency.
• Foundation for future features - The added JSON-RPC methods and new HTTP endpoints for Moonraker lay the groundwork for future integrations and remote interactions. These additions improve the extensibility of the API for upcoming features.
• Reusable helpers - New helper methods for checking whether a process is running and computing the SHA-256 hash of a file provide core utility functions that can be reused throughout the codebase.
• Improved configuration - By adding new sections to BlocksScreen.cfg, users have more flexibility and control over how the system behaves without modifying source code

Tests

Tested with standard testcases,
Missing Unit and Integration Tests,

Delete section if not applicable.

Future work

Creating unit and integration tests for all endpoints created