Update the make:publication command

[caendesilva]

Refactors the make:publication command to fix bugs and provide a consistent console UI layer.

Fixes:

• Don't ask users to fill in meta fields
• Fix bug causing booleans to not be fillable (presumably as writing true to STDIN is the same as writing 'true')
• Indent empty collection warnings
• Normalize output styles for messages to enter array and text input
• Add message when skipping a field?
• Test that fields that have a required rule cannot be skipped
• Unset skipped values when generating front matter?
• Check if we should use $field->getValidationRules() instead of $field->type->rules() as it seems we might be missing checking custom rules
• When using php hyde make:publication foo and there are no publications at all, the current message "Error: Unable to locate any publication types. Did you create any?" might not be entirely relevant.
• Fix integers are serialized as strings
• Make sure that the proper type is selected when asked

[codecov]

Codecov Report

Merging #786 (b8588ab) into publications-feature (f9f30f7) will decrease coverage by 0.11%.
The diff coverage is n/a.

@@                    Coverage Diff                     @@
##             publications-feature     #786      +/-   ##
==========================================================
- Coverage                  100.00%   99.88%   -0.12%     
+ Complexity                   2796     1406    -1390     
==========================================================
  Files                         324      162     -162     
  Lines                        7028     3541    -3487     
==========================================================
- Hits                         7028     3537    -3491     
- Misses                          0        4       +4     

Impacted Files	Coverage Δ
...rk/src/Console/Commands/MakePublicationCommand.php	95.95% <0.00%> (-4.05%)	⬇️
...rc/Framework/Actions/CreatesNewPublicationPage.php	100.00% <0.00%> (ø)
...rc/Console/Commands/Helpers/InputStreamHandler.php
...rk/src/Console/Commands/MakePublicationCommand.php
...rc/Framework/Actions/CreatesNewPublicationPage.php
.../src/Console/Commands/RebuildStaticSiteCommand.php
...rk/Features/Publications/PublicationFieldTypes.php
...ework/src/Framework/Services/ValidationService.php
...kages/framework/src/Foundation/RouteCollection.php
...amework/src/Console/Concerns/ValidatingCommand.php
... and 154 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[caendesilva]

Fix bug causing booleans to not be fillable (presumably as writing true to STDIN is the same as writing 'true')

According to the docs (https://laravel.com/docs/9.x/validation#rule-boolean)

"The field under validation must be able to be cast as a boolean. Accepted input are true, false, 1, 0, "1", and "0"."

Just extracting bools to a helper method that casts to bool changes the generated YAML from name: '1' to name: true f4a5887

Not sure how to allow strings without losing custom validation rules and without too much added code

Edit: Think I figured it out b3303aa but we might want to extract that to a custom validation rule that we can swap out the standard one for

Resources: https://github.com/illuminate/validation/blob/3f63f1046f67377a64779baaa86d7f1997b5f748/Concerns/ValidatesAttributes.php#L448-L453
https://laravel.com/docs/9.x/validation#rule-boolean

[caendesilva]

Some things left to do, moving todos to #685