CAMEL-22943: Remove deprecated camel-google-pubsub-lite component

[sandeepGenz]

Description

Removes the deprecated camel-google-pubsub-lite component from the codebase.

The component was deprecated in Camel 4.10 following Google Cloud Platform's deprecation
of the underlying Pub/Sub Lite service.

Users should migrate to:

• camel-google-pubsub → Google Cloud Pub/Sub
• camel-kafka → Google Cloud Managed Service for Apache Kafka

Changes

• Deleted components/camel-google/camel-google-pubsub-lite/ module
• Removed from components/camel-google/pom.xml, bom/camel-bom/pom.xml, catalog/camel-allcomponents/pom.xml, parent/pom.xml, coverage/pom.xml
• Removed google-cloud-pubsublite-version property from parent/pom.xml
• Removed from MojoHelper.java component path list
• Deleted generated catalog JSON, docs page, example JSON, DSL builders
• Updated docs/components/modules/ROOT/nav.adoc
• Added removal notice to camel-4x-upgrade-guide-4_19.adoc

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.

[davsclaus]

you need to regen these files also in this PR

	modified:   catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components.properties
	modified:   core/camel-main/src/generated/resources/org/apache/camel/main/components.properties
	modified:   dsl/camel-componentdsl/src/generated/java/org/apache/camel/builder/component/ComponentsBuilderFactory.java
	modified:   dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/EndpointBuilderFactory.java
	modified:   dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/EndpointBuilders.java
	modified:   dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/StaticEndpointBuilders.java
	modified:   dsl/camel-kamelet-main/src/generated/resources/camel-component-known-dependencies.properties

[sandeepGenz]

@davsclaus should it be through the script, or manual file changes also works for the regen?

[sandeepGenz]

@davsclaus i did lookup in the codebase, should i do ./etc/scripts/regen.sh (full script) for the regen?

[davsclaus]

yeah if you run that script it does a full regen