chore(contributing): remove note about eslint-config-next

Since we don't prefer having ESLint as part of the examples anyway.

Author: balazsorban44

contributing/examples/adding-examples.md

@@ -7,7 +7,7 @@ When you add an example to the [examples](examples) directory, please follow the
 - If API routes aren't used in an example, they should be omitted
 - If an example exists for a certain library and you would like to showcase a specific feature of that library, the existing example should be updated (instead of adding a new example)
 - Package manager specific config should not be added (e.g. `resolutions` in `package.json`)
-- In `package.json` the version of `next` (and `eslint-config-next`) should be `latest`
+- In `package.json` the version of `next` should be `latest`
 - In `package.json` the dependency versions should be up-to-date
 - Use `export default function` for page components and API Routes instead of `const`/`let` (The exception is if the page has `getInitialProps`, in which case [`NextPage`](https://nextjs.org/docs/api-reference/data-fetching/get-initial-props#typescript) could be useful)
 - CMS example directories should be prefixed with `cms-`