Add "just" recipes and aliases for runing bin-artifacts.

This allows for much more convenient cmd binary launching without the need
to remember distinction bitween binaries in main crate (hagrid) and
others (hagridctl, tester) and need to provide additional -- to cargo to
pass arguments to binaries.

Apart from convenience it also provide kinda "documentation" of binary
artifacts in the project as "run" group in just collect all the
artifacts together.

Changes:
- Add new named aliases for `just run` which runs "hagrid" binary with web
  server:
  - run-hagrid
  - hagrid
- Add new recipe to run "hagrid-delete" binary "run-hagrid-delete".
- Alias "run-hagrid-delete" recipe as
  - hagrid-delete
  - delete
- Add new recipe to run "hagridctl" crate with default binary
  "run-hagridctl".
- Alias "run-hagridctl" recipe as
  - hagridctl
- Add new recipe to run "tester" crate with default binary "run-tester".
- Alias "run-tester" recipe as
  - tester

justfile

@@ -146,6 +146,30 @@ run:
     cargo run
 
 alias r := run
+alias run-hagrid := run
+alias hagrid := run
+
+# Run "hagrid-delete" binary which deletes (address, key)-binding(s), and/or a key(s).
+[group('run')]
+run-hagrid-delete *args:
+    cargo run --bin hagrid-delete -- {{ args }}
+
+alias hagrid-delete := run-hagrid-delete
+alias delete := run-hagrid-delete
+
+# Run "hagridctl" which automate some operations working with database externally, e.g. import keys
+[group('run')]
+run-hagridctl *args:
+    cargo run --package hagridctl -- {{ args }}
+
+alias hagridctl := run-hagridctl
+
+# Run "tester" which allows to seed database with sample data, e.g. for testing
+[group('run')]
+run-tester *args:
+    cargo run --package tester -- {{ args }}
+
+alias tester := run-tester
 
 # Clean compilation artifacts (i.e. "target" directory)
 [group('clean')]