anchor.diff:  <3> It is possible to inject beans from our test deployment directly into the test case
   <4> This method directly invokes the health check Servlet and verifies the response
   <5> This method uses the injected health check bean to verify it is returning the expected result
  -
  -
  -
  -// end::main[]
  
positive.code: 
  This means that metadata is only processed once at build time, which both saves on startup time, but also on memory
  usage as the classes etc that are used for processing are not loaded (or even present) in the runtime JVM.
  
  
  == Three Phases of Bootstrap and Shamrock Philosophy
  
  
negative.code:     process. Any retained objects that are produced in this stage will be directly serialized into the native image.
      This means that if a framework can boot in this phase then it will have its booted state directly written to the
      image, so the boot code does not need to be executed when the image is started.
  +
  There are some restrictions on what can be done in this stage as Substrate disallows some objects in the native image,
  for example you should not attempt to listen on a port or start threads in this phase.
  +
  In JVM mode there is no real difference between this and runtime init, except that this is always executed first.
  
  Runtime Init::
      If bytecode is recorded with `@Record(RUNTIME_INIT)` then it is executed from the application's main method. This code
  