Mount `/app/.blueprint/dev` directory by default for extension development

[prplwtf]

While this could be manually set every time someone uses Blueprint docker for extension development, I think there's no harm in mounting the /app/.blueprint/dev directory by default to somewhere accessible by the user.

I'm not great at docker, hence why I turned this into an issue.

---

I assume it would just be editing

docker/docker-compose.yml

Lines 107 to 114 in 466511a

	volumes:
	- "${BASE_DIR}/var/:/app/var/"
	- "${BASE_DIR}/nginx/:/etc/nginx/http.d/"
	- "${BASE_DIR}/certs/:/etc/letsencrypt/live:ro" # Remove the ":ro" at the end if generating certs automatically
	- "${BASE_DIR}/logs/:/app/storage/logs"
	- "${BASE_DIR}/nginx/logs:/var/log/nginx"
	- "${BASE_DIR}/extensions/:/blueprint_extensions"
	- "app:/app"

to add

- "${BASE_DIR}/logs/:/app/.blueprint/dev" 

---

The .blueprint/dev directory exists after the bash blueprint.sh step in setting up Blueprint. Not sure if this complicates things, but thought it was good to mention.

(feedback is really appreciated)