Review integration digest computation and projection to the integration container as env var

### What happened?

Since an integration digest ends up begin [projected as a container env var](https://github.com/apache/camel-k/blob/9c058daa180106fb5b770558f9b553b7bfb9d2ef/pkg/trait/container.go#L181), [including the traits when computing the digest](https://github.com/apache/camel-k/blob/9c058daa180106fb5b770558f9b553b7bfb9d2ef/pkg/util/digest/digest.go#L111) has a number of side effects, as example by enabling/disabling the creation of a route or service, would lead to the container to be restarted which is not expected.

### Steps to reproduce

_No response_

### Relevant log output

_No response_

### Camel K version

_No response_

Start with pkg/trait/container.go at the projection of the integration digest as a container environment variable, then read pkg/util/digest/digest.go around digest computation and trait inclusion. Review how trait changes affect the digest and determine a behavior that avoids unexpected container restarts; done means the digest projection and computation no longer produce those side effects.

Written by the indexing model from the issue text.