Refactor Cilium CNI installation

[tico88612]

What type of PR is this?

/kind design
/kind feature

What this PR does / why we need it:

We would deprecate the old template installation, and using the Cilium CLI will be better.

Which issue(s) this PR fixes:

Fixes #12049 #12153
Related #11487

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Cilium CNI installation replaces Jinja template with Cilium CLI
[action required] `cilium_agent_custom_args` and `cilium_operator_custom_args` are deprecated, please use `cilium_agent_extra_args` and `cilium_operator_extra_args`.
[action required] `cilium_identity_allocation_mode` default change to `crd`.
[action required] `cilium_enable_host_legacy_routing` default change to `false`.
Add CIlium hubble export advanced flow log settings (`cilium_hubble_export_file_max_backups`, cilium_hubble_export_file_max_size_mb`, `cilium_hubble_export_dynamic_enabled` and `cilium_hubble_export_dynamic_config_content`)
Deprecated `cilium_ipsec_node_encryption`, replace it with `cilium_encryption_node_encryption`

[tico88612]

/ok-to-test

[tico88612]

For the extended cilium test.

/label ci-extended

[tico88612]

/label tide/merge-method-merge

[tico88612]

/retest-failed

[tico88612]

/retest-failed

[VannTen]

I didn't review thoroughly yet, I'll see if I can find the time.
Since this is a relatively big change (right ?) do we want to hold this one until after 2.28, to have more testing time in master before a release ?

[tico88612]

@VannTen Selfishly, I hope it will be released on 2.28 (I'm not sure if Cilium 1.15 is compatible with Kubernetes 1.32), but if it requires a lot of testing (it's too close to the K8s 1.33 release), I agree with your idea.

[VannTen]

I don't have strong opinions on this, and I also don't have a production stake (as our clusters are not on cilium) ; so maybe other more involved in cilium / using it could chime in ?

[tmurakam]

/lgtm

[tmurakam]

This is the last blocking issue of #12175 (Release proposal of 2.28.0)
Can anyone review and approve this PR?

[VannTen]

I haven't reviewed the diff in detail, but I don't see anything immediatly wrong and since there has been review by @tmurakam already, let's merge this.

Thanks everyone for all the work 🎉
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RaulButuc, tico88612, VannTen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [VannTen]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tmurakam]

@VannTen
Thank you!