Remove or repurpose the type field in the controls section of the Everest configuration

[verveerpj]

Is your feature request related to a problem? Please describe.
The type field in the controls section of the Everest configuration is not used and can be removed or re-purposed.

Describe the solution you'd like
We should investigate if this field is indeed not used for anything meaningful. We will likely find that this field is very often specified in existing configuration files, but not used in any way. Based on this information, we can decide if we want to remove it, or repurpose it within the context of this issue: #9537.

Describe alternatives you've considered
We could leave it as is, it would not affect functionality.

[DanSava]

The control type is being used for config validation

ert/src/everest/config/everest_config.py

Lines 449 to 465 in cb0726d

	@model_validator(mode="after")
	def validate_variable_name_match_well_name(self) -> Self: # pylint: disable=E0213
	controls = self.controls
	wells = self.wells
	if controls is None or wells is None:
	return self
	well_names = [w.name for w in wells]
	if not well_names:
	return self
	for c in controls:
	if c.type == "generic_control":
	continue
	for v in c.variables:
	if v.name not in well_names:
	raise ValueError("Variable name does not match any well name")
	return self

This can be updated such that either all variable variables match well names or none not sure if there is an edge case where we want some of the variable names in a control to match some of the names of the wells if the wells are present in the config.