feat: add prettier for content folder

[saimonkat]

Description

This PR adds prettier config for content folder

Problems

Commets sctructure

Before

To comment out content in a markdown file we used JSX-style comments

{/* 

content

*/}

This approach had a problem that we could see the commented code in the markdown preview, but allowed us to comment huge complicated blocks of code.

After

Unfortunately, Prettier escapes asterisks and formats JSX comments from {/* ... */} to {/\* ... \*/}.
It looks bad, provides build and eslint errors, and there is nothing we can do about it.

So now we're changing to the new comments structure:

[comment]: <> (This is a single line comment.)

[comment]: <> (
This is a multiline comment.
You can't use line breaks here.
You should escape the () brackets with a \ backslash.
)

This new approach allows to hide the commented code from the markdown preview, but has a big problem that we can't comment complicated blocks of codes.

We still can use JSX-style comments for the complicated blocks of codes, but in this case we should add the whole file to prettier ignore list at .prettierignore

Updated contribution guide

Steps to test

• ensure that all Docs pages are the same as before
• ensure that all Guides pages are the same as before
• ensure that Flow page is the same as before

References
Preview

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
neon-next	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 13, 2024 9:16pm

[rishi-raj-jain]

@saimonkat

I see that you requested my review on this.

Is the PR ready and no longer in draft mode?

[saimonkat]

Hi @rishi-raj-jain I just wanted you to take a look at this and hear you thoughts about comments issue, I described in description 🙏🏻