Add warning about js-ipfs being discontinued / point to Helia in a few places

[ElPaisano]

Describe your changes

Addresses #1465 and Part 1 of issue 1459

Checklist before requesting a review

• Passing the beta version of the Check Markdown links for modified files check. Action results can be viewed here.

Checklist before merging

• Passing all required checks (The beta Check Markdown links for modified files check is not required)

[ElPaisano]

@2color I added this callout in the following places:

Install IPFS for JavaScript (js-ipfs) https://bafybeieznadnxgmxf6bhhiofwzgorcyz7ysarn42737xlv7mphtg6gqrcu.on.fleek.co/install/js-ipfs/
IPFS Implementations https://bafybeieznadnxgmxf6bhhiofwzgorcyz7ysarn42737xlv7mphtg6gqrcu.on.fleek.co/concepts/ipfs-implementations/
Create a simple chat app https://bafybeieznadnxgmxf6bhhiofwzgorcyz7ysarn42737xlv7mphtg6gqrcu.on.fleek.co/how-to/create-simple-chat-app/
IPFS repository guide > Protocol implementations https://bafybeieznadnxgmxf6bhhiofwzgorcyz7ysarn42737xlv7mphtg6gqrcu.on.fleek.co/project/repository-guide/#fetch-or-contribute-to-ipfs-code

Any other spots you think we ought to add this in?

[2color]

I would move this either to below the table or into the js-ipfs row so it's not the first thing you read on the page.

Also, this is the first time I've seen slated used this way. Looking it up reveals that it's a north American word which probably explains why I haven't seen it. What do you think about a more neutral verb, e.g. scheduled or planned?

[2color]

The new warning element itself is great.

I would also add it to the following pages:

• https://docs.ipfs.tech/reference/js/api/
• https://docs.ipfs.tech/concepts/nodes/#js-ipfs

[2color]

Either here or in a separate PR, e.g. #1360, we should add Helia to the list of implementation

[ElPaisano]

Either here or in a separate PR, e.g. #1360, we should add Helia to the list of implementations

👍 made a note to address it as part of #1465, will create a quick PR