feat: support JSON5 task files alongside YAML

[josegonzalez]

Summary

Task files may now be authored in JSON5, with format selected by the file extension (.yml / .yaml for YAML, .json / .json5 for JSON5). When --tasks is omitted, docket probes tasks.yml, tasks.yaml, then tasks.json in source order. JSON5 is a strict superset of JSON so existing JSON files parse unchanged; the JSON5 extras (// and /* */ comments, trailing commas, unquoted keys) make hand-authored recipes more comfortable.

apply, plan, validate, init, and fmt all accept either format. init infers the surface from the --output extension. fmt round-trips JSON5 comments via an in-tree comment-aware AST so the canonical layout is identical between the YAML and JSON5 surfaces.

Closes #218.

[dokku-bot]

sh-checker report

To get the full details, please check in the job output.

shellcheck errors

shellcheck checking is disabled.

shfmt errors

'shfmt -l -d -i 2' returned error 1 finding the following formatting issues:

----------
tests/bats/task_file_json.bats
diff tests/bats/task_file_json.bats.orig tests/bats/task_file_json.bats
--- tests/bats/task_file_json.bats.orig
+++ tests/bats/task_file_json.bats
@@ -70,7 +70,7 @@
 
 @test "docket auto-detects tasks.json when no --tasks flag is given" {
   cd "$BATS_TEST_TMPDIR"
-  cat > tasks.json <<'EOF'
+  cat >tasks.json <<'EOF'
 [
   {
     tasks: [
@@ -87,7 +87,7 @@
 
 @test "docket prefers tasks.yml over tasks.json when both exist" {
   cd "$BATS_TEST_TMPDIR"
-  cat > tasks.yml <<'EOF'
+  cat >tasks.yml <<'EOF'
 ---
 - tasks:
     - name: yaml-task
@@ -94,7 +94,7 @@
       dokku_app:
         app: api
 EOF
-  cat > tasks.json <<'EOF'
+  cat >tasks.json <<'EOF'
 [
   { tasks: [{ name: "json-task", dokku_app: { app: "api" } }] },
 ]
----------

You can reformat the above files to meet shfmt's requirements by typing:

  shfmt -l -d -i 2 -w filename