Cannot set GOMAXPROCS

[squakez]

Recently we're suffering the failed to set GOMAXPROCS from cgroups error in the CI. Likely there was some hardware change in the github actions infrastructure as this problem happens suddenly withouth any change on our side. However, we had this problem in the past in local environments. I wonder if we can just skip the setting instead of panicking and not being able to run the operator. I think it is a good fallback strategy in situations where there are hardware changes that are out of control of the Camel K operator users.