Add scope+include/exclude support in mojo

Description of the issue:

all dependencies of the mojo are added to the images

Expected behavior:

dependencies should be filterable, common way for maven is

1. scope
2. explicit includes/excludes (g:a:v[:t:c])

[chanseokoh]

@rmannibucau @natlovewy2535

As promised, the Jib Extension Framework is now available with the latest Jib versions. You can easily extend and tailor the Jib plugins behavior to your liking.

We’ve written a general-purpose layer-filter extension that enables fine-grained layer control, including deleting files and moving files into new layers. The extension will cover your use-case to filter unwanted dependencies (or any files).

• Maven Layer-Filter Extension
• Gradle Layer-Filter Extension

For general information about using and writing extensions, take a look at the Jib Extensions repo.

[rmannibucau]

For reference profiles is not an option cause it requires rebuilds and is not release compatible whereas multiplying artificially modules work but slows down the build with no gain (why bypassing jib plugin to use core programmatically is saner).