small fix to remove the option of generating a wasm tm client

[charleenfei]

Description

part of the work in #4801

Commit Message / Changelog Entry

type: commit message

see the guidelines for commit messages. (view raw markdown for examples)

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against correct branch (see CONTRIBUTING.md).
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards and Go style guide.
• Wrote unit and integration tests.
• Updated relevant documentation (docs/) or specification (x/<module>/spec/).
• Added relevant godoc comments.
• Provide a commit message to be used for the changelog entry in the PR description for review.
• Re-reviewed Files changed in the Github PR explorer.
• Review Codecov Report in the comment section below once CI passes.

[codecov-commenter]

Codecov Report

Merging #4814 (5a62616) into cian/merge-main-wasm (e9c0862) will increase coverage by 0.08%.
Report is 4 commits behind head on cian/merge-main-wasm.
The diff coverage is n/a.

Additional details and impacted files

@@                   Coverage Diff                    @@
##           cian/merge-main-wasm    #4814      +/-   ##
========================================================
+ Coverage                 79.78%   79.87%   +0.08%     
========================================================
  Files                       189      189              
  Lines                     13264    13249      -15     
========================================================
- Hits                      10583    10582       -1     
+ Misses                     2254     2242      -12     
+ Partials                    427      425       -2     

see 1 file with indirect coverage changes

[damiannolan]

We can remove this too?

Were all of the other fields also removed? I believe there was something attached to the Coorindator struct specfic to wasm clients also

[colin-axner]

ACK, but there's other logic that can be removed as well, such as chain.SetWasm()

[charleenfei]

ACK, but there's other logic that can be removed as well, such as chain.SetWasm()

ACK, but there's other logic that can be removed as well, such as chain.SetWasm()

pulling on threads and unravelling -- ill push these changes to this pr as well!

[colin-axner]

closing as changes are included in #4804