Consider supporting bootRun task rather than exec-ing bootJar directly

[davidconnard]

I have a project in which I'd like to use this plugin ... however, the base bootJar is not easily runnable for us, as it needs a whole lot of environment variables setup, including some complex logic to determine correct local values of those env vars. We use the gradle bootRun task to do all of this for us - gradle bootRun is how we run the applicational locally, not java -jar bootJar.

So - this is a feature request to consider more flexibility around the forkedSpringBootRun task ... is it viable to make this an execution of the bootRun task instead? I can see a couple of possible options for this ... including forking a whole new process (like the bootJar) task, or possibly, declaring dependencies on this with doFirst {} declarations within the forkedSpringBootRun task (and making this task a no-op) instead?

I'm not clear on what the best approach would be to achieve what we need. I'd have a crack at a PR for it ... but I'm not sure what you, the project maintainers, would consider the best approach either. So, I figured I may as well just ask here ... :) Thanks!