Fix ignite tests when Ipv6 is used (on Jenkins ppc64le)

[apupier]

due to a limitation with ignite
apache/ignite#10648 , when Ipv6 is used a path with a too long name is created causing this kind of error:

Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
create page store work directory:
/home/jenkins/712657a4/workspace/l_Camel_Core_Build_and_test_main/components/camel-ignite/ignite/work/db/0_0_0_0_0_0_0_1_lo_127_0_0_1_140_211_168_51_172_17_0_1_2605_bc80_3010_500_2ae2_df68_ddb5_b30d_enp0s1_2605_bc80_3010_500_49b6_174f_c257_989b_enp0s1_2605_bc80_3010_500_5c75_1cd_c31b_18bb_enp0s1_2605_bc80_3010_500_6901_e190_8428_d693_enp0s1_2605_bc80_3010_500_8701_f209_ec6e_1b7b_enp0s1_2605_bc80_3010_500_bfd3_a0e3_608c_e985_enp0s1_2605_bc80_3010_500_f816_3eff_fea2_6bbc_enp0s1_2605_bc80_3010_500_fdff_edb6_e567_8ce2_enp0s1_47500
	at org.apache.ignite.internal.util.IgniteUtils.ensureDirectory(IgniteUtils.java:10028)

the workaround used is to override the node naming

Description

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.