Accept compiler options when building app

[miorimmax]

• Please check if the PR fulfills these requirements

• There is an open issue describing the problem that this pr intents to solve.
  • You have a descriptive commit message with a short title (first line).
• Tests for the changes have been added (for bug fixes / features).
• Docs have been added / updated (for bug fixes / features).

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  Feature

• What is the current behavior?
  We don't have a mechanism to provide compiler options to the Clojure compiler.

• What is the new behavior (if this is a feature change)?
  We can provide compiler options to the Clojure compiler using the --compiler-options OPTIONS command line argument, whose value is a map in EDN format (i.e. anything that clojure.edn/read-string can read).

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
  This PR does not introduce breaking changes.

• Other information:
  Closes: Vessel lacks a mechanism to set options for the Clojure compiler #33

[miorimmax]

Looks like the PR checks are not triggering for some reason, anything I should do?

[alan-ghelardi]

lgtm. I'll have a look why the Action didn't trigger 😕

[alan-ghelardi]

I changed the workflow to trigger on pull_request events. Could you rebase onto the main branch, please? Also, most likely, you'll need to enable actions on your fork if they aren't enabled by default. Last, if possible, add a new entry to the changelog with a brief explanation about your change. Just put a new Added section under the Unreleased one. When we trigger a release, the changelog is bumped automatically.

[alan-ghelardi]

I'm just requesting a change in the changelog to avoid breaking the release process. The feature itself is fine.