[Tooling] chore: add destrictive warning to docker_w*pe target

[bryanchriswhite]

Description

The docker_wipe make target is quite a destructive action as it destroys all containers, images, and volumes in docker. This includes things unrelated to the pocket and requires the user to re-download any docker images they may require, which can be very time consuming. Additionally, there is the potential to lose data in the destruction of the volumes. I think it's especially important that we provide a sufficient warning as we're including its usage in developer documentation.

Issue

No open issue.

Type of change

Please mark the relevant option(s):

• New feature, functionality or library
• Bug fix
• Code health or cleanup
• Major breaking change
• Documentation
• Other: chore: improve developer experience

List of changes

• Add appropriately scary warning to the docker_wipe target via a new phony dependency

Testing

• make develop_test
• LocalNet w/ all of the steps outlined in the README

Required Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have tested my changes using the available tooling
• I have updated the corresponding CHANGELOG

If Applicable Checklist

• I have updated the corresponding README(s); local and/or global
• I have added tests that prove my fix is effective or that my feature works
• I have added, or updated, mermaid.js diagrams in the corresponding README(s)
• I have added, or updated, documentation and mermaid.js diagrams in shared/docs/* if I updated shared/*README(s)