chore(content/update): Refactor and Amend Weld Message

[psavidis]

Content

• Refactor Weld Informative message to be more clearly phrased
• Add a message to state the workaround limitations (cross-archive references)

Related-to: camunda/camunda-bpm-platform#4499

[tasso94]

Where can I find the installation guide hint?

[psavidis]

Where can I find the installation guide hint?

❓ I couldn't find a relevant section to add the hint. Where do you think the weld info could fit in the subcategories of the Tomcat Installation guide ?

[psavidis]

Update

After applying the code review suggestion the formatting of the text didn't feel right.
I've added a commit to add new line characters to make the formatting more structurally appealing.

Here are the Before / After Screenshots to ease up the review process:

Before

After

PS: The same change was applied to the Patch Level Update Section

[tasso94]

❓ I couldn't find a relevant section to add the hint. Where do you think the weld info could fit in the subcategories of the Tomcat Installation guide ?

Let's glue a note box to the installation guide where we repeat the information for Tomcat 10.

Maybe something along the following lines:

{{< note title="Known Limitations in Tomcat 10" class="info" >}}

**<h4>Weld Class Loading Issues</h4>**

In deployment scenarios involving one or more process applications with managed beans, classloading issues may occur if the WELD library is directly embedded in the WAR's `/WEB-INF/lib` folder.
To resolve this, move the weld library away from the war and place it into the `$CATALINA_HOME/lib` folder.

The above fix is not guaranteed to work for cases with bean references between WAR deployments (WAR A referencing a bean from WAR B). 

The following test scenarios fail on Tomcat 10:

* [CallActivityContextSwitchTest](https://github.com/camunda/camunda-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/context/CallActivityContextSwitchTest.java)
* [CdiBeanCallActivityResolutionTest](https://github.com/camunda/camunda-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/cdi/CdiBeanCallActivityResolutionTest.java)
{{< /note >}}

Should be part of the 7.21 installation guide as well.

[psavidis]

❓ I couldn't find a relevant section to add the hint. Where do you think the weld info could fit in the subcategories of the Tomcat Installation guide ?

Let's glue a note box to the installation guide where we repeat the information for Tomcat 10.

Maybe something along the following lines:

{{< note title="Known Limitations in Tomcat 10" class="info" >}}

**<h4>Weld Class Loading Issues</h4>**

In deployment scenarios involving one or more process applications with managed beans, classloading issues may occur if the WELD library is directly embedded in the WAR's `/WEB-INF/lib` folder.
To resolve this, move the weld library away from the war and place it into the `$CATALINA_HOME/lib` folder.

The above fix is not guaranteed to work for cases with bean references between WAR deployments (WAR A referencing a bean from WAR B). 

The following test scenarios fail on Tomcat 10:

* [CallActivityContextSwitchTest](https://github.com/camunda/camunda-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/context/CallActivityContextSwitchTest.java)
* [CdiBeanCallActivityResolutionTest](https://github.com/camunda/camunda-bpm-platform/blob/f37877b822dabcbf3cee5806bd5833d18cdcb543/qa/integration-tests-engine/src/test/java/org/camunda/bpm/integrationtest/functional/cdi/CdiBeanCallActivityResolutionTest.java)
{{< /note >}}

Should be part of the 7.21 installation guide as well.

Applied the suggested change. Will follow up with the 7.21 backport once this PR is finalised and merged.

[tasso94]

Looks good now 🙂 👍 I replaced the word fix with workaround.