[Cases] Move disabling features to the cases context

[cnasikas]

Summary

Solutions that use Cases may want to disable some features cases provide. For example in Observability the sync of alerts is disabled. This is achieved with prop drilling. This PR enhances the code by creating a features object that is available through the CasesContext. This way in the future we can disable/enable more futures without having to pass props down to the components.

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/security-threat-hunting-cases (Team:Threat Hunting:Cases)

[cnasikas]

@elasticmachine merge upstream

[jonathan-buttner]

Sooo much cleaning than the prop drilling nice work! I left a few questions and suggestions.

[semd]

Nice! I would only suggest moving the initialization of the state inside a function so we prevent calling merge when it is not needed. Right now the merge result is only used the first render but it is computed every time, if we move it inside a function in the useState parameter React will only call it once:

Suggested change

	/**
	* The empty object at the beginning avoids the mutation
	* of the DEFAULT_FEATURES object
	*/
	const featuresOptions = merge({}, DEFAULT_FEATURES, features);
	const [value, setValue] = useState<CasesContextStateValue>({
	owner,
	userCanCrud,
	basePath,
	features: featuresOptions,
	const [value, setValue] = useState<CasesContextStateValue>(() => ({
	owner,
	userCanCrud,
	basePath,
	features: merge({}, DEFAULT_FEATURES, features),
	}));

[cnasikas]

I am not sure if that is correct. The JS engine will execute the merge function but React will not gonna reset the value after the first render. I change it because it is more readable :)

[semd]

The JS engine will execute the merge function but React will not gonna reset the value after the first render

exactly https://reactjs.org/docs/hooks-reference.html#lazy-initial-state

[semd]

Though the last change did no difference because the initialValue parameter is still an object. The change I was suggesting is to replace the object for a function returning the object, this way the merge will only be executed in the first render.
Anyway, the merged features configs are pretty small by now, the optimization will not have a big impact. It is okay as it is 👍

[semd]

The code in general LGTM! I left a couple of suggestions, but it is up to you @cnasikas to do it or not, I am good with how the code is now too. Thanks for the improvement 🚀

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 43ac5ff
• Storybooks Preview

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
cases	353	354	+1

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
cases	414	421	+7

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
cases	300.1KB	300.0KB	-120.0B
observability	360.6KB	360.5KB	-7.0B
timelines	202.9KB	202.9KB	+12.0B
total			-115.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
cases	85.3KB	85.4KB	+112.0B

Unknown metric groups

API count

id	before	after	diff
cases	455	463	+8

History

• 💚 Build #10615 succeeded 4f7896b
• 💚 Build #10067 succeeded 3bd0588
• 💚 Build #9918 succeeded 0f2432a
• 💔 Build #9739 failed 1fbe20e726c7a5c15a35192e2693993cba89ca7f

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @cnasikas