Add error handling and troubleshooting guide for Klaystagram dApp

[ChinonyeRuth]

This commit introduces a new section titled "Error Handling and Troubleshooting" to the Klaystagram dApp documentation. This section aims to assist developers in identifying and resolving common errors they might encounter during development and testing.

The new section covers the following:

Transaction Failures: Explains potential causes and debugging tips for transaction failures, including insufficient funds and smart contract errors.

Connection Issues: Addresses common causes and solutions for connection issues between the application and the blockchain node.

Other Errors: Provides general debugging strategies such as reviewing error messages, consulting documentation, using debugging tools, and seeking help from online communities.

By incorporating this error-handling guide, the Klaystagram documentation becomes more comprehensive and user-friendly, empowering developers to effectively troubleshoot and navigate potential challenges during the development process.

Proposed changes

• Describe your changes to communicate to the maintainers why we should accept this pull request.
• If it fixes a bug or resolves a feature request, be sure to link to that issue.

Types of changes

Please put an x in the boxes related to your change.

• [ ] Minor Issues and Typos
• [x] Major Content Contribution
• [ ] Others

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to reach out. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [ ] I have read the CONTRIBUTING GUIDELINES
• [ ] I have signed the CLA
• [ ] I have added necessary documentation (if appropriate)
• [ ] Any dependent changes have been merged and published in downstream modules

Related issues

• Please leave the issue numbers or links related to this PR here.

Further comments

If this is a relatively large content contribution, kick off the discussion by explaining why you would suggest the content contribution, etc...

[ChinonyeRuth]

I have read the CLA Document and I hereby sign the CLA

[scott-klaytn]

Thank you for your contribution! Due to repository migration, we're closing this PR for now. We plan to reopen contributions in the new Kaia docs repo once it's public. We encourage you to resubmit your PR there then.