add test-solidity to github actions, create test script

[noot]

Closes: #XXX

Description

• create CI job that runs the initializable and initializable-buidler solidity tests
• these are currently the only 2 tests that pass fully (shall we make this a required check?)

---

For contributor use:

• 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.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer

---

For admin use:

• Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
• Reviewers assigned
• Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

[codecov]

Codecov Report

Merging #510 into development will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           development     #510   +/-   ##
============================================
  Coverage        70.49%   70.49%           
============================================
  Files               41       41           
  Lines             2325     2325           
============================================
  Hits              1639     1639           
  Misses             543      543           
  Partials           143      143           

Impacted Files	Coverage Δ
app/ethermint.go	92.30% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 517de55...10079e9. Read the comment docs.

[J-Thompson12]

Whoops i approved then saw the solidity tests failed. I am leaving the approval because i am pretty sure the solidity test fail has nothing to do with this pr.

[noot]

@J-Thompson12 for some reason the initializable-buidler test is failing here but passing for me locally, could you try running it and let me know what happens?