Distribution EOLE

Ease the choice between EOLE standard volume extension and custom

The administrator should be able to easily choose between EOLE
standard volume extension and a custom one.

It also must:

- be separated with the new LV creation
- not clash with the meaning of “0” in manual LV creation which should
do nothing

• dicos/00_partitioning.xml: new variable
  “use_eole_standard_volume_extension” automatically filled and
  customisable by the administrator
  The “test_extend_standard_partitioning” variable do not need to be
  calculated based on “lv_names” anymore, this avoid a infinite recursion.

• creole/funcs/partitioning_utils.py (check_partitioning_auto_extend):
  remove the now unused parameter “lv_names”.

• pretemplate/00-partitioning: simplify the logic, we have mostly two
  choices now.

Ref: #21647

We do not need to redefine “partitioning_create_lv” anymore

The EOLE standard volume extension mechanism is handle by a new variable.

• dicos/30_amon.xml: remove the redefinition

Ref: #21647

We do not need to redefine “partitioning_create_lv” anymore

The EOLE standard volume extension mechanism is handle by a new variable.

• dicos/30_eclair.xml: remove the redefinition.

Ref: #21647

We do not need to redefine “partitioning_create_lv” anymore

The EOLE standard volume extension mechanism is handle by a new variable.

• dicos/30_hapy-node.xml: remove the redefinition.

Ref: #21647

We do not need to redefine “partitioning_create_lv” anymore

The EOLE standard volume extension mechanism is handle by a new variable.

• dicos/30_scribe.xml: remove the redefinition.

Ref: #21647

We do not need to redefine “partitioning_create_lv” anymore

The EOLE standard volume extension mechanism is handle by a new variable.

• dicos/30_sphynx.xml: remove the redefinition.

Ref: #21647

We do not need to redefine “partitioning_create_lv” anymore

The EOLE standard volume extension mechanism is handle by a new variable.

• dicos/30_thot.xml: remove the redefinition.

Ref: #21647