Always use same description for EnableException

[andreasjordan]

Type of Change

• [ ] Bug fix (non-breaking change, fixes # )
• [ ] New feature (non-breaking change, adds functionality, fixes # )
• [ ] Breaking change (affects multiple commands or functionality, fixes # )
• [ ] Ran manual Pester test and has passed (.\tests\manual.pester.ps1)
• [ ] Adding code coverage to existing functionality
• [ ] Pester test is included
• [ ] If new file reference added for test, has is been added to github.com/dataplat/appveyor-lab ?
• [ ] Unit test is included
• [x] Documentation
• [ ] Build system

Sometimes I stumble across different descriptions for the same parameter. I would like to harmonize the descriptions for the very frequently used parameters and then set them consistently.

As most commands already used the same description for EnableException, I changed the other commands accordingly.

[potatoqualitee]

Thank you 🙇🏼