BED-5495: Add Dozzle Container Log Viewer to Development Environment

[neumachen]

Description

This PR adds the Dozzle container log viewer to our development environment and updates the README.md with documentation about this new tool. Dozzle provides a web-based interface for viewing and searching container logs,
making it easier for developers to debug issues without using command-line tools.

The changes include:

1 Adding a new Dozzle service to docker-compose.dev.yml
2 Standardizing volume definitions in docker-compose.dev.yml using explicit empty object notation
3 Adding documentation about Dozzle to the README.md under a new "Development Tools" section

Motivation and Context

This PR addresses: BED-5495

Developers need to use command-line tools like docker logs to view container output, which can be cumbersome when working with multiple services. Dozzle provides a clean web interface that allows developers to view
logs from all containers in real-time, filter logs by container, search within logs, and download logs for sharing or offline analysis.

The standardization of volume definitions improves readability and follows Docker Compose best practices.

Why is this change required? What problem does it solve?

How Has This Been Tested?

Testing included:

• Starting the development environment with docker-compose -f docker-compose.dev.yml up
• Verifying that the Dozzle service starts correctly
• Accessing the Dozzle web interface at http://dozzle.localhost
• Confirming that logs from all containers are visible and searchable
• Testing the configuration with custom environment variables (BH_DOZZLE_HOSTNAME and BH_DOZZLE_PORT)
• Verifying that all volumes function correctly with the updated syntax

Screenshots:

Types of changes

• Chore (a change that does not modify the application functionality)
• New feature (non-breaking change which adds functionality)

Checklist:

• I have met the contributing prerequisites
  • Assigned myself to this PR
  • Added the appropriate labels
  • Associated an issue: Issues and Pull Requests README #672
  • Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing
• I have ensured that related documentation is up-to-date
  • Open API docs
  • Code comments (GoDocs / JSDocs)
• I have followed proper test practices
  • Added/updated tests to cover my changes
  • All new and existing tests passed