Adds Go package to get contracts, transactions, and scripts

[joshuahannan]

Closes: #18

Description

Adds additional code to the go package to be able to return contracts and transactions.
I would like to use embed instead of go-bindata because that seems to be easier to maintain and use.

Still working on adding and testing the rest of the transactions and scripts

The bridge standup code in main.go is commented out for now to allow for testing.

---

For contributor use:

• Targeted PR against main branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the standards mentioned here.
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.35%. Comparing base (02aab3f) to head (faae363).
Report is 219 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #163      +/-   ##
==========================================
+ Coverage   86.19%   87.35%   +1.15%     
==========================================
  Files          18       18              
  Lines         884     1020     +136     
==========================================
+ Hits          762      891     +129     
- Misses        122      129       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[joshuahannan]

@sisyphusSmiling Do you have an idea about why the CI test is failing? I don't think I made any changes to that test and it is passing locally.

Also, I updated to the latest version of flow CLI, and it is now generating a lcov.info. I assume that is just another coverage related thing, so I just added it to .gitignore.

[sisyphusSmiling]

@joshuahannan looks like the last successful tests passed in a prior version of Flow CLI - v2.2.3 vs v2.2.4. I'll pull down this branch and replicate locally

[sisyphusSmiling]

Pushed a fix. @joshuahannan I'm not sure what happened here. The failing test case expected the foo trait serialized as nil, but the trait has always had a value of bar and so should always have been serializable. Odd that CI didn't fail until the recent changes which had nothing to do with the failing files. I wonder if there were changes in the way AnyStruct is serialized in Cadence that were included in the latest CLI release? Looks like Cadence v1.3.0 included onflow/cadence#3594 which implemented FLIP 293 - this very well could have affected serialization patterns.

I updated the test case to expect the serialized value in 8eceb59