[BUG] Fix eslint warnings on whole examples

Describe the bug

All examples has a known eslint warning like following:

const container = document.getElementById("root");
const root = createRoot(container!); // this line throw null-assertion warning

It can be solved like this:

const container = document.getElementById("root");
// eslint-disable-next-line
const root = createRoot(container!); // this line throw null-assertion warning

Also, some variables, types or functions are declared but not using.

Steps To Reproduce

1. npm run bootstrap
2. npm run bootstrap -- --scope "example-name"
3. npm run start -- --scope "example-name"
4. Shows eslint warnings and errors in the terminal.

Expected behavior

The examples run with no lint warnings or errors.

Screenshot

No response

Desktop

No response

Mobile

No response

Additional Context

No response

[sevkioruc]

Thanks for your explanation @salihozdemir 😃

[salihozdemir]

The main reason for using the eslint is because every developer has own style of writing (like naming conventions/tabs/single or double quotes for a string). With different styling techniques, your codebase may look weird, more error-prone and vulnerable. For these reasons we don’t want to ignore eslint.

Thanks @sevkioruc for helping us to maintain the code standard. 🚀