docs: Added eslint markdown plugin and fixed all critical errors

[pweglik]

Description

Added eslint markdown plugin to format code blocks in docs using our eslint config.
I corrected critical errors (mostly "...") so blocks are correctly formatted.
It also generates a lot of new warnings (no-unused-vars) - we can safely ignore most of them, but when you produce new piece of docs you should monitor them, if they can be safely ignored, or did you misspell the variable you declared before that. We cannot enable no-undef-vars because it produces too many warnings (every JSX tag etc.), so we have to rely on those no-unused-vars warnings:

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (improves or adds clarity to existing documentation)

Related issues

Checklist

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly
• My changes generate no new warnings - they do

Additional notes

[pweglik]

to tylko dlatego, że wywalało sie jakieś jedno randomo miejsce w TextEmbeddingsModule.md, nie chce mi się rozkminiać dlaczego więc errcor -> warning chwilowo

[jakmro]

Could you write wich line caused the error?

[pweglik]

It is super weird - I'm not really sure why is it bothered by All_MINILM_L6_V2_TOKENIZER but not by ALL_MINILM_L6_V2. Super weird so I decided not to spend time on it

[msluszniak]

You can use // eslint-disable-next-line camelcase for only this line

[pweglik]

It will be visible in docs then. I'd say we don't want

import {
  TextEmbeddingsModule,
  ALL_MINILM_L6_V2,
  // eslint-disable-next-line
  All_MINILM_L6_V2_TOKENIZER,
} from 'react-native-executorch';

// Loading the model
await TextEmbeddingsModule.load(ALL_MINILM_L6_V2, All_MINILM_L6_V2_TOKENIZER);

// Running the model
const embedding = await TextEmbeddingsModule.forward('Hello World!');

in our docs right?

[mkopcins]

yep, not the cleanest look, especially since it is not an error present in the code itself

[mkopcins]

this doesn't seem correct, maybe add some more code around this to make this correct

[pweglik]

I've added useExecutorchModule so it feels more natural

[mkopcins]

either do this way or '...' like below to keep it consistent

[pweglik]

fixed