Configure the Container lifecycle based on the Test events

A user should be able to customize how he wants the Container to be controlled.

The default behavior is:
@BeforeSuite -> container.start()
@BeforeClass -> container.deploy()
@AfterClass -> container.undeploy()
@AfterSuite -> container.stop()

Other scenarios are:

• Restart server pr test class
  @BeforeClass -> container.start()
  @BeforeClass -> container.deploy()
  @AfterClass -> container.undeploy()
  @AfterClass -> container.stop()

• Redeploy pr test method
  @BeforeSuite -> container.start()
  @Before -> container.deploy()
  @After -> container.undeploy()
  @AfterSuite -> container.stop()

• Restart pr test method
  @Before -> container.start()
  @Before -> container.deploy()
  @After -> container.undeploy()
  @After -> container.stop()

This could be done by adding a Engine configuration option
e.g.:
engine/containerLifeCycle PrSuite|PrClass|PrMethod

this option would map to different ContextAppenders in the background that does the setup/ordering.