JIT: add support for xtensa (esp32)

[pguyot]

These changes are made under both the "Apache 2.0" and the "GNU Lesser General
Public License 2.1 or later" license terms (dual license).

SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[bettio]

My idea was to approve it, but actually it fails in CI, I think that now tests are taking too longer after xtensa addition.

[pguyot]

My idea was to approve it, but actually it fails in CI, I think that now tests are taking too longer after xtensa addition.

We can bump timeouts or disable jit tests for other archs when jit is enabled. This reduces coverage a little bit (jit compiler itself is an interesting bit of code to jit compile) but it would benefit CI processing time overall.