Move e2e tests to independent folder

[shaspitz]

Closes #219

[mpoke]

Nice work @smarshall-spitzbart. I didn't check the functionality, since I guess it's just a refactoring, right?

At the moment the structure is a bit hard to follow, maybe a README.md would help, i.e.,

• setup_test.go -- setup for the e2e tests
• common_test.go -- helper functions
• channel_init_test.go -- e2e tests for the Channel Initialization sub-protocol
• valset_update_test.go -- e2e tests for the Validator Set Update sub-protocol
• unbonding_test.go -- e2e tests for the Completion of Unbonding Operations
• slashing_test.go -- e2e tests for the Consumer Initiated Slashing sub-protocol
• distribution_test.go -- e2e tests for the Reward Distribution sub-protocol
• stop_consumer_test.go -- e2e tests for the Consumer Chain Removal sub-protocol

Move to valset_update.go the content from bonding_test.go and vsc_test.go.

Move to channel_init_test.go the content from genesis_test.go, ibc_test.go, history_test.go, proposal_test.go.

distribution_test.go will be empty for now.

Re. the 4 different ...TestSuites data structure, I think we can have only one, but let's do that in a separate PR.

[shaspitz]

Nice work @smarshall-spitzbart. I didn't check the functionality, since I guess it's just a refactoring, right?

At the moment the structure is a bit hard to follow, maybe a README.md would help, i.e.,

• setup_test.go -- setup for the e2e tests
• common_test.go -- helper functions
• channel_init_test.go -- e2e tests for the Channel Initialization sub-protocol
• valset_update_test.go -- e2e tests for the Validator Set Update sub-protocol
• unbonding_test.go -- e2e tests for the Completion of Unbonding Operations
• slashing_test.go -- e2e tests for the Consumer Initiated Slashing sub-protocol
• distribution_test.go -- e2e tests for the Reward Distribution sub-protocol
• stop_consumer_test.go -- e2e tests for the Consumer Chain Removal sub-protocol

Move to valset_update.go the content from bonding_test.go and vsc_test.go.

Move to channel_init_test.go the content from genesis_test.go, ibc_test.go, history_test.go, proposal_test.go.

distribution_test.go will be empty for now.

Re. the 4 different ...TestSuites data structure, I think we can have only one, but let's do that in a separate PR.

You're correct that I didn't change any test functionality in this PR, I only moved things around.

Your mentioned file organization sounds great to me, thank you! My only correction to your proposed solution is that I believe TestTrackHistoricalInfo should go in its own file under normal_operations_test.go, since it doesn't relate to channel initialization. A new readme was added to the e2e test directory.

Lastly I've opened #300 to address the fact that we have a lot of redundant code in setup_test.go.

[mpoke]

Great work.