Setting up syntax highlighting of code section - Configuration fix for Examples

[AdrieanKhisbe]

Description

Complement #5259, getConfigs was not correctly forwarded to Examples 🖇️
As a result, syntax highlight could not be disabled be disabled or configured in that element as was reported by @mariem-89

Motivation and Context

Achieve expected behavior introduced in #5259

How Has This Been Tested?

Ran the test locally and performed local acceptance tests (see screenshots)

Screenshots (if appropriate):

Before / After

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.

[AdrieanKhisbe]

🔄 (rebased on top on up to date master, and fixed typo in commit message)

[tim-lai]

@AdrieanKhisbe Thanks for the followup fix!

[AdrieanKhisbe]

You're welcome @tim-lai :)
Thanks for you too for your reactivity!! 🙂