feat(quickstart): fix broker InconsistentClusterIdException issues

[hsheth2]

Our previous Docker volume declaration was at too high a level in the file tree, which meant that the actual data was stuck in docker anonymous volumes instead of our named volume. As such, those volumes would be lost, causing zookeeper to start fresh instead of loading it's previous state. The kafka broker, which retained its state correctly, would then throw an InconsistentClusterIdException.

Repro - this sequence now works, whereas it didn't before.

datahub docker quickstart -f <file>
# ingest sample data
datahub docker quickstart --stop
datahub docker quickstart -f <file>

Closes #9047.

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[shirshanka]

LGTM. Great fix!