Introduce bean scopes for scan and recipe

[fabapp2]

Scoped Spring Beans

Some objects must exist only once per application, these are a perfect fit for singleton-scoped beans.
But, some other beans have a lifetime shorter than the application itself.
Additionally, these should exist once per thread that executes (theoretically, because static instances currently prevent parallel threads).

ExecutionContext

OpenRewrite's ExecutionContext is such a class.
The ExecutionContext is populated with data available on every new scan, e.g. Maven configuration information.
Additionally, it contains data with a potentially shorter lifespan (of a recipe execution), e.g. error information or messages.

Moving the creation and destruction (or clean up) of the ExecutionContext to Spring would simplify usage and code.
Clients could just inject the current instance using Spring and the ExecutionContext is not required to be passed down the object tree.

By providing a dedicated scope like recipe-scope it would be possible to inject the "right" instance (scoped to current thread and recipe execution) to all objects that share the same or narrower lifespan (Recipe, Action(s), Conditions, ...)

public MyAction {
   // The context from current 'recipe-scope' will be injected
   @Autowired
   private ExecutionContext ctx;
}

OpenRewrite populates data to the ExecutionContext as early as during the scan of an application.

From SBM's perspective, the ExecutionContext contains data with different scopes: scan and recipe-execution.

This means either:

1. The ExecutionContext is created on each recipe execution and the data normally set during scan (in OR) is kept and passed to the ExecutionContext when the first recipe gets executed. This could be done by keeping this data in a bean scoped to scan which is then used to create ExecutionContexts when a recipe starts.
2. The ExecutionContext has itself a scope of scan and the bean is recreated on each scan. The data with a shorter lifespan needs to be removed after each recipe execution

RewriteMavenParser

The RewriteMavenParser reads the .mvn/maven.config from project root. This makes this class a scan-scoped bean.
It has to be recreated on each new scan of a project. It also requires access to the ExecutionContext.

[fabapp2]

The ExecutionContext is also required in ApplicableRecipeListCommand. This prevents the ExecutionContext lifetime to span a recipe run only.

• Messages added while evaluating recipe conditions would be lost when the recipe runs and a new ExecutionContext is created

[fabapp2]

Another attempt...

• ExecutionContext has scan scope instead.
  • Existing ExecutionContext is removed from scope.
  • A new ExecutionContext gets created on each scan.
• During condition evaluation new messages can be added to the ExecutionContext.
• Recipes can add messages to the ExecutionContext. These messages must be removed after every recipe run
• The messages that were added during parsing/scan must be kept until a new condition evaluation or finishing a recipe run