anchor.diff:  object at runtime.
   
   In more detail, a processor class from the extensions deployment module gathers the configuration
  -information within a @BuildStep` method that is also annotated with a `@Record(STATIC_INIT)` or  `@Record(RUNTIME_INIT)` annotation along with injection of a `@Template` annotated class
  +information within a `@BuildStep` method that is also annotated with a `@Record(STATIC_INIT)` or  `@Record(RUNTIME_INIT)` annotation along with injection of a `@Template` annotated class
   from the runtime module. A class annotated with `@Template` is known as a template because it
   provides a template of methods to configure a runtime service. The value of template that is
   injected into the deployment class is a proxy of the template, and any method invocations that are made will be recorded, and output as bytecode that will be run at application startup.
  
positive.code: == Maven setup
  
  Your extension project should be setup as a multi-module project with two submodules:
  1. A deployment time submodule that handles the build time processing and bytecode recording.
  2. A runtime submodule that contains the runtime behavior that will provide the exentsion behavior in the native image or runtime JVM.
  
  Your runtime artifact should depend on shamrock-core-runtime, and possibly the runtime artifacts of other Shamrock
  
negative.code: ----
  <1> Note that there is no @Inject qualifier here. This is a feature of the CDI implementation used by the Shamrock core to process @ConfigProperty only available to the deployment time extension.
  
  The value of these properties is configured in a `META-INF/microprofile-config.properties` file that conforms to the MicroProfile config format.
  
  An extension of MicroProfile config to allow configuration objects to be injected is available using the `@org.jboss.shamrock.runtime.ConfigGroup` annotation. You place this annotation on the configuration object which in turn uses @ConfigProperty for it's configurable values as follows:
  
  