added another example about converter extension

[jonathanlukas]

Camunda Community Hub Pull Request Template

Description

Additional context

Testing your changes

Types of changes

• Bug fix (non-breaking change which fixes an existing open issue)
• New feature (non-breaking change which adds functionality to an extension)
• Breaking change (fix or feature that would cause existing functionality of an extension to change)
• Documentation update (changes made to an existing piece of documentation)

Checklist:

• My code adheres to the syntax used by this extension.
• My pull request requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the Camunda Community Hub documentation.
• I have read the Pull Request Process documentation.
• I have added or suggested tests to cover my changes suggested in this pull request.
• All new and existing CI/CD tests passed.
• I will /assign myself this issue, and add the relevant [issue labels] to it if they are not automatically generated by Probot.
• I will tag @camunda-community-hub/devrel in a new comment on this issue if 30 days have passed since my pull request was opened and I have not received a response from the extension's maintainer.

[github-actions]

Test Results

 28 files  + 28   28 suites  +28   1m 20s ⏱️ + 1m 20s
251 tests +251  251 ✅ +251  0 💤 ±0  0 ❌ ±0 
372 runs  +372  372 ✅ +372  0 💤 ±0  0 ❌ ±0 

Results for commit e62cd8d. ± Comparison against base commit 3a17ec5.

♻️ This comment has been updated with latest results.