chore: bump hermes to v1.8.0

[faddat]

Description

Works on issue:

• Integration testing between major cosmos repositories cosmos-sdk#12228

This PR updates hermes to v1.7.4 and ensures that hermes is not using a feature branch fork.

---

Author Checklist

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.

I have...

• Included the correct type prefix in the PR title
• Added ! to the type prefix if state-machine breaking change (i.e., requires coordinated upgrade)
• Confirmed this PR does not introduce changes requiring state migrations, OR migration code has been added to consumer and/or provider modules
• Targeted the correct branch (see PR Targeting)
• Provided a link to the relevant issue or specification
• Followed the guidelines for building SDK modules
• Included the necessary unit and integration tests
• Added a changelog entry to CHANGELOG.md
• Included comments for documenting Go code
• Updated the relevant documentation or specification
• Reviewed "Files changed" and left comments if necessary
• Confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed this PR does not introduce changes requiring state migrations, OR confirmed migration code has been added to consumer and/or provider modules
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage

[faddat]

@jtremback those changes happened because of changes in the docker image used.

[faddat]

@jtremback I'm going to flip this back to a draft, I have to update the configuration used for Hermes because I've now updated this to v1.6.0

[faddat]

@jtremback - I think that the remaining issue, may be related to either the new relayer software, or test code, and I also think that it may work fine on a second run.

[mpoke]

LGTM

[faddat]

maybe