Suggest alternatives when active recipes are not found

[timtebeek]

What's changed?

When active recipe(s) not found, provide a helpful Did you mean: ... of closest match.

What's your motivation?

Misconfigurations are common and hard to spot, as seen in supporting OSS and even colleagues.
In particular when generated Refaster recipes are used, folks might fail to add the Recipe or Recipes suffix.
By providing the nearest match as a suggestion folks have an easier way to troubleshoot this themselves.

Anything in particular you'd like reviewers to focus on?

1. I'd expect calls to Environment#activateRecipes(Iterable<String> activeRecipes) to be rare enough to be ok with the streams use there. Outside perhaps tests I'd expect that to be called once per recipe run. Calling that out for review.
2. We already have a dependency on commons-lang3, which has the getLevenshteinDistance we use here. Didn't want to add a new dependency just for that, but in theory it's deprecated. In practice we're unlikely to move to a new major version any time soon.

Have you considered any alternatives or workarounds?

We could use a different method of providing alternatives.

Any additional context

This came up twice today; once in OSS and once internally; combined time savings would already have paid this off today.

[timtebeek]

Also discussed on Slack; I'll take "makes sense" as approval to merge.