When you permanently destroy a specific project from the command line, the following
additional good things now happen:
- the direct orhpan milestones are removed too
(instead of leaving them orphan, broken, invisible forever)
- all children projects emerge like cute bubbles by one level
(instead of having them orphan, broken, invisible forever)
- the parent project is eventually restored as "without sub-projects"
(instead of having a broken root-project with bugged memberships)
This change has nothing to do with archived projects.
This change will only affect future usages of the destroy workflow, that is:
./bin/remove destroy PHID-OF-YOUR-PROJECT-TO-BE-DESTROYED
Example initial situation:
```
Project A
[projectDepth: 0]
[hasSubprojects: 1]
[members: *automatic*, foo, bar]
> Project B
[projectDepth: 1]
[hasSubprojects: 1]
[members: *automatic*, foo, bar]
> Project C
[hasSubprojects: 0]
[projectDepth: 2]
[members: foo, bar]
```
Situation after destroying only project A:
```
Project B
[projectDepth: 0]
[hasSubprojects: 1]
[members: *automatic*, foo, bar]
> Project C
[projectDepth: 1]
[hasSubprojects: 0]
[members: foo, bar]
```
Situation after destroying only project B:
```
Project A
[projectDepth: 0]
[hasSubprojects: 1]
[members: *automatic*, foo, bar]
> Project C child of project B
[projectDepth: 1]
[hasSubprojects: 0]
[members: foo, bar]
```
Situation after destroying only project C:
```
Project A
[projectDepth: 0]
[hasSubprojects: 1]
[members: *automatic*, foo, bar]
> Project B
[projectDepth: 1]
[hasSubprojects: 0]
[members: foo, bar]
```