Update tools dependency

[AdityaSripal]

Commit that referred to tools dependency does not exist in git history because of force push. Update go.mod to refer to latest commit

• Linked to github-issue with discussion and accepted design OR link to spec that describes this work.
• Wrote tests
• Updated relevant documentation (docs/)
• Added a relevant changelog entry: clog add [section] [-t <tag>] [-m <msg>]
• Re-reviewed Files changed in the github PR explorer

---

For Admin Use:

• Added appropriate labels to PR (ex. wip, ready-for-review, docs)
• Reviewers Assigned
• Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

[mircea-c]

LGTM.

Technically runsim is not a dependency of the project, but it is easier to have it in go.mod rather than having to ensure it never gets committed by anyone by mistake.

[codecov]

Codecov Report

Merging #4801 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4801      +/-   ##
==========================================
- Coverage    50.5%   50.49%   -0.02%     
==========================================
  Files         288      288              
  Lines       18518    18518              
==========================================
- Hits         9353     9351       -2     
- Misses       8480     8482       +2     
  Partials      685      685

[AdityaSripal]

agree with @colin-axner . since these files will change after go mod tidy, i think it makes sense to just have sdk developers adopt workflow so that they always run go mod tidy before a merge

Otherwise, we will have commits that either add or remove meaningless dependencies to SDK

Thoughts? @mircea-c

ran go mod tidy

[alexanderbez]

ACK