Added app: ipfs-chat

[SomajitDey]

What kind of PR is this?

Select only one to speed up review/approval; i.e., don't lump an addition and a removal into a single PR.

• Adding something new to awesome-ipfs
• Editing something already listed on awesome-ipfs
• Removing something from awesome-ipfs
• Something else (if so, please explain in the "Additional details" section below)

Pre-submit checklist

Please confirm ALL of the following before submitting your PR.

• This PR includes only one addition, removal, or edit.
• I edited the /data directory instead of the README.md.
• I reviewed the content policy and the and the IPFS Community Code of Conduct to ensure my submission meets the requirements.
• I have followed the CONTRIBUTING.md guidelines.

Additional details

Is there anything else we should know about this PR?

There are lots of excellent chat applications using WebRTC and JS-IPFS, all requiring signaling servers, some not very easy to install. So, going along a different track, decided to build a very basic chat app that

1. uses only standard GNU/Linux command-line tools and the Go-IPFS CLI
2. doesn't need any special server like the WebRTC apps
3. works over both LAN and internet (including NAT traversal)
4. provides secure chatrooms, private messaging and in-chat file & directory sharing

ipfs-chat achieves all these and is run from a single Bash script !

For new additions: What is your project's current size/reach?

• Github stars: 21 (As of Aug 21,2021)
• Support received in different fora: reddit, discuss.ipfs.io
• Activity: Commits are frequent

For new additions: What is your project's potential size/reach?

For new additions: How critical is IPFS to your project?

• Essential
• Somewhat critical
• Useful, but not critical

For new additions: What core goal(s) does your project address?

• Big-data solutions
• Freedom from corporate/government interference
• Data integrity
• Dev tools or other ways to enable developers
• Disaster resilience/recovery
• File storage/retrieval
• File streaming
• Permanent archiving
• Self-sovereign identity
• Platforms that utilize consensus, reputation, or incentivization
• Encrypted messaging
• Encrypted file and directory sharing

Is anything about IPFS blocking your project?

• Inability to load changes to config without restarting the IPFS daemon. Ref
• Inability to limit bandwidth. Ref
• Inability to add protected peers without restarting IPFS daemon. Ref

[welcome]

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions
  and stakeholders linked/mentioned.

• Your contribution itself is clear (code comments, self-review for the
  rest) and in its best form. Follow the code contribution
  guidelines
  if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

• A maintainer will triage and assign priority to this PR, commenting on
  any missing things and potentially assigning a reviewer for high
  priority items.

• The PR gets reviews, discussed and approvals as needed.

• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!