Add camel 4.8 LTS docs to website (#1233)

* Add camel 4.8 LTS docs to website

* Prepare docs for website publish

* Prepare docs for website publish

* Prepare docs for website publish

* Prepare docs for website publish

antora-playbook-snippets/antora-playbook.yml

@@ -17,10 +17,9 @@ content:
     - url: https://github.com/apache/camel.git
       branches:
         - main
+        - camel-4.8.x
         - camel-4.4.x
-        - camel-4.0.x
         - camel-3.22.x
-        - camel-3.21.x
       start_paths:
         # eip
         - core/camel-core-engine/src/main/docs
@@ -33,29 +32,24 @@ content:
       branches:
         - main
         - release-2.4.x
-        - release-2.3.x
-        - release-2.2.x
       start_path: docs
 
     - url: https://github.com/apache/camel-k-runtime.git
       branches:
         - main
-        - release-3.2.x
         - release-3.8.x
       start_path: docs
 
     - url: https://github.com/apache/camel-kamelets.git
       branches:
         - main
         - 4.4.x
-        - 4.0.x
       start_path: docs
 
     - url: https://github.com/apache/camel-quarkus.git
       branches:
         - main
         - 3.8.x
-        - 3.2.x
       start_path: docs
 
     - url: https://github.com/apache/camel-quarkus-examples.git
@@ -65,18 +59,16 @@ content:
     - url: https://github.com/apache/camel-kafka-connector.git
       branches:
         - main
-        - camel-kafka-connector-4.0.x
       start_paths:
         - docs
         - connectors
 
     - url: https://github.com/apache/camel-spring-boot.git
       branches:
         - main
+        - camel-spring-boot-4.8.x
         - camel-spring-boot-4.4.x
-        - camel-spring-boot-4.0.x
         - camel-spring-boot-3.22.x
-        - camel-spring-boot-3.21.x
       start_paths:
         - components-starter
         - core
@@ -86,7 +78,6 @@ content:
     - url: https://github.com/apache/camel-karaf.git
       branches:
         - camel-karaf-3.22.x
-        - camel-karaf-3.21.x
       start_path: docs
 
 ui:

content/blog/2023/08/camel-k-micrometer/index.md

@@ -26,7 +26,7 @@ Metrics are generated by two types of sources:
 
 Since Micrometer provides a facade, the changes in the default metrics from the libraries powered by camel components will depend on what they expose.
 
-Before Camel K 2.0, the [default camel metrics](/components/3.21.x/microprofile-metrics-component.html#_default_camel_metrics) where provided by the camel Microprofile Metrics component. Now they [default camel metrics](/components/next/micrometer-component.html#_default_camel_metrics) are provided by the Micrometer Component. As you can see in the documentations, there are some changes in the naming and the metrics.
+Before Camel K 2.0, the default camel metrics where provided by the camel Microprofile Metrics component. Now they default camel metrics are provided by the Micrometer Component. As you can see in the documentations, there are some changes in the naming and the metrics.
 
 
 > **_NOTE:_**  There has been some recent change in the Micrometer Camel component on naming conventions so depending on your camel version you can expect **'CamelExchangesTotal'** to change to **'camel.exchanges.total'** starting from Camel 4. Please refer to the [compatibility matrix](/camel-k/next/index.html#_camel_dependencies_matrix) to know which version of Camel is used.

content/blog/2023/09/camel-karavan-4.0.0/index.md

@@ -40,7 +40,7 @@ We recognize the importance of a straightforward development process. With Karav
 
 ## Camel-main
 
-[Camel-main](/components/4.0.x/others/main.html) (aka standalone) runtime became the primary runtime implementation in this release. Its appeal lies in its pure Apache Camel nature, which requires no external dependencies/runtimes or additional configurations, thus reducing complexity and streamlining your integration projects. You can focus on building robust and efficient integrations without the burden of managing complex runtime environments. It aligns perfectly with the philosophy of Apache Camel Karavan — making integration development straightforward and efficient.
+[Camel-main](/components/next/others/main.html) (aka standalone) runtime became the primary runtime implementation in this release. Its appeal lies in its pure Apache Camel nature, which requires no external dependencies/runtimes or additional configurations, thus reducing complexity and streamlining your integration projects. You can focus on building robust and efficient integrations without the burden of managing complex runtime environments. It aligns perfectly with the philosophy of Apache Camel Karavan — making integration development straightforward and efficient.
 
 ## Version Updates
 

content/blog/2024/02/camel-whatsapp-langchain4j/index.md

@@ -8,7 +8,7 @@ preview: "Build a conversational AI integration with Apache Camel, LangChain4j,
 ---
 
 
-This blog shows how Apache Camel can help integrate multiple systems with an AI model, in particular, the [camel-whatsapp](/components/4.0.x/whatsapp-component.html) component is used to build a chat on WhatsApp; so that a user can easily communicate with the LLM (large Language Model) via WhatsApp.
+This blog shows how Apache Camel can help integrate multiple systems with an AI model, in particular, the camel-whatsapp component is used to build a chat on WhatsApp; so that a user can easily communicate with the LLM (large Language Model) via WhatsApp.
 
 
 # Overview
@@ -31,7 +31,7 @@ In this example, the model [GPT-3.5 Turbo](https://platform.openai.com/docs/mode
 This is the hardest part, if you would like to test it by yourself some requirements need to be fulfilled before executing the code, in particular:
 
 
-* A business WhatsApp account is needed, for development purposes this is free, you can follow the documentation in the [Camel WhatsApp component](/components/4.0.x/whatsapp-component.html)
+* A business WhatsApp account is needed, for development purposes this is free, you can follow the documentation in the Camel WhatsApp component
 * An OpenAI API key, the [LangChain4j getting started](https://github.com/langchain4j#getting-started) contains information how to generate the API key
 * [Webhook](https://developers.facebook.com/docs/whatsapp/cloud-api/guides/set-up-webhooks) needs to be configured in the WhatsApp business account, so that way WhatsApp API can communicate with the running Apache Camel application
 * If you are testing locally, the running application's webhook has to be exposed to the internet, for example via [ngrok](https://ngrok.com/)