Add Pint, PHP-CS-Fixer, and reconfigure

[driftingly]

This PR moves Duster's coding standards away from Tighten Coding Standard and introduces Laravel Pint.

Laravel Pint has appeared as the de facto standard for code style and fixes for the Laravel community. We extend Pint's Laravel preset to add some Tighten-specific rules.

Since Pint is built around rules that can be automatically fixed, we'll still rely on PHP_CodeSniffer to catch issues that require manual intervention. Most of these come from PSR1.

This PR also relies on a custom PHP-CS-Fixer rule to order class elements. This can be removed as soon as this PR from @bakerkretzmar is merged or Pint allows additional customizations.

Notable Changes

The duster init command is no longer required. Duster will use any config files if they exist but will fall back to passing Duster's own config file.

To replace generating GitHub Actions via the init command a new github-actions command has been added.

Duster now accepts path arguments which can be passed in when using Duster with Husky and lint-staged:

duster app/Http/Controllers/UserController.php app/Http/Controllers/Controller.php

Supplied paths with a specific tool:

duster tlint app/Http/Controllers/UserController.php app/Http/Controllers/Controller.php

The GitHub action stub now runs duster instead of each tool separately.

The help command received colours:

---

Once merged it will deprecate Tighten Coding Standard and allows TLint to focus on things these tools cannot do.

Closes tighten/tlint#294
Closes tighten/tlint#290
Closes tighten/tlint#280
Closes tighten/tlint#161

[sbine]

Nice work! 👍 from me as soon as the one suggestion is addressed