Gradlew not longer used to run dev version of lf cli tools

[axmmisaka]

This PR fixes #1909.

Right now, we have two ways of executing lfc (mutatis mutandis for lfd and lff):

1. Use the script built by gradle located in build/install/lf-cli/bin/
2. Use gradlew to invoke cli:lfc:run, which is handled by ./bin/lfc

The issue is these two methods handle strings differently - specifically, gradlew will parse strings again. If we do not distinguish them and use them interchangeably, we will get screwed (#1909 )

This PR renames the executables in ./bin by adding a -dev suffix to them, to distinguish them from any installed artifacts that may already be on the PATH. In addition, the scripts have been simplified by not letting Gradle handle the invocation of lfc, lfd, etc. because this leads to problems like the one reported in lf-lang/playground-lingua-franca#81 because Gradle swallows exit codes.

[lhstrh]

1. Whether to use `./gradlew cli:lfc:run`

2. Should we have `./bin` and `./utils` at all

We've talked about this at quite some length, and the consensus was that it was OK to have these script, but they shouldn't have the same name as the executables built for production (which Gradle places in the build directory).

We resolved to just add -dev to the names of these helper scripts so that there wouldn't be any confusion between installed artifacts and ad-hoc built ones. This question about file names and placement, however, is orthogonal to the change suggested in this PR.

[lhstrh]

Related: lf-lang/playground-lingua-franca#81

[lhstrh]

Let's go ahead and merge this so that other problems dependent on this can be worked on.

[axmmisaka]

Let's squash merge this commit because it's relatively small and most commits are small cosmetic surgery.

[lhstrh]

It's already on the merge queue...

[cmnrd]

Using --quiet is a very good idea! However, by dropping the -p it is now not possible anymore to run lfc-dev from an arbitrary directory. For me, this was the main reason for using the script instead of the corresponding gradle run command. I will provide a fix in another PR.