Add Dymension IBC relayers information

[svv28]

Description

I decided to add Dymension IBC relayers information. it contains the same info, as chain-registry repo[https://github.com/cosmos/chain-registry/tree/master/_IBC], but added information about channels operators.
Every community member, who is operating IBC for Dym could add his info. It is useful information in case:
estimation of the member' actual part in relayeing for FDP,
in case of the stucked packets in particular channel it could be address request to responsible community member.

beside that discord bot could be added for automation ping of the Relayer. (Archway use this practice)

This info could be use as official reference for IBC relayer' operators. and the link to this git folder could be pinned in Relayers discord Channel.

Hope it would be useful

---

Closes #XXX

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow-up issues.

PR review checkboxes:

I have...

• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Targeted PR against the correct branch
• included the correct type prefix in the PR title
• Linked to the GitHub issue with discussion and accepted design
• Targets only one GitHub issue
• Wrote unit and integration tests
• Wrote relevant migration scripts if necessary
• All CI checks have passed
• Added relevant godoc comments
• Updated the scripts for local run, e.g genesis_config_commands.sh if the PR changes parameters
• Add an issue in the e2e-tests repo if necessary

SDK Checklist

• Import/Export Genesis
• Registered Invariants
• Registered Events
• Updated openapi.yaml
• No usage of go map
• No usage of time.Now()
• Used fixed point arithmetic and not float arithmetic
• Avoid panicking in Begin/End block as much as possible
• No unexpected math Overflow
• Used sendCoin and not SendCoins
• Out-of-block compute is bounded
• No serialized ID at the end of store keys
• UInt to byte conversion should use BigEndian

Full security checklist here

----;

For Reviewer:

• Confirmed the correct type prefix in the PR title
• Reviewers assigned
• Confirmed all author checklist items have been addressed

---;

After reviewer approval:

• In case the PR targets the main branch, PR should not be squash merge in order to keep meaningful git history.
• In case the PR targets a release branch, PR must be rebased.

[omritoptix]

thanks for that! we'll review the idea and respond soon.

[svv28]

any updates on this PR?

[github-actions]

This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you!