Camel-k 2.9.0 fails mounting configmap with dots in the name.

[Exether]

Bug description

Hello,

I'm testing our integrations with 2.9.0 and I noticed a regression on how configmap and secret are mounted.
Consider the attached objects (configmap + integration).
integrationWithConfigmap.yaml

The integration will start fine in camel-k 2.8.0 but fail with 2.9.0 (doesn't start because it can't find configmap).
Having a look at the corresponding deployment we see that the issue comes from the fact 2.9.0 is using an incorrect reference to the configmap (left 2.8.0 / right 2.9.0):

Camel K or runtime version

2.9.0

[squakez]

Probably introduced by this sanitization: #6379 - we'll work to fix it in 2.9.1.