Update quarkus-bon-jova dependency from app to 0.4.0

[hannotify]

I had to make these changes to make mvn install work from the root dir. WDYT?

[holly-cummins]

Hm, I see what's happened, but I'm not sure what's the best fix. When I configured the release, I had it perform the release on the extension module, because I didn't think there was any value in releasing the sample app. However, that means that the release plugin didn't roll the version numbers on the app. The release itself would succeed, but I guess subsequent builds then started failing.

I can see the following options:

• Keep the app using a release version, and add dependabot to keep the release number up to date. This keeps everything working, but it means when we run locally, we're not running against the version we're making changes to, which probably is what we want.
• Also release the sample app, by changing the project structure to have it be inside the module
• Use a parent pom and some versions and maven config to allow the sample app to use the current version, without hardcoding a release version. The integration tests don't get released but do use the local version, so we may be able to copy that.

Whatever we do, though, it can wait until after the first live demo. I've raised #133 so we don't forget.