Table-Driven-Tests (TDT) improvement to remove context initialization

[lumtis]

#540 (comment)

Many unit tests we use in our codebase use Table Driven Tests (TDT)
The idea is to create a table of test cases containing input, expected output for better maintainability and visualisation.

In many of these tests, we perform first initialization before the table declaration. Most of the time, initialization of coordinators, chains, etc...
This context initialization makes our tests less in the idea of TDT where the whole purpose of a test case should be visualized in the test case itself and make the tests less visual and maintainable.

The idea would be to investigate how we could incorporate the context initialization in the test case itself as the initial state of the test case. For example, describing the list of coordinators in the test case, the coordinators are then initialized in the body of the TDT

Example:

[coordinators initialization]
[chains initialization]

foreach []testCase{
  {
    input
    expectedOutput
  }
  ....
} {
  [assertion]
}

would become

foreach []testCase{
  {
    initialState{
      coordinators
      chains
    }
    input
    expectedOutput
  }
  ....
} {
  [coordinators initialization]
  [chains initialization]
  [assertion]
}

Implementation example:

Test for claim CompleteMission:

spn/x/claim/keeper/mission_test.go

Line 63 in d828285

func TestKeeper_CompleteMission(t *testing.T) {

I'm open to any feedback, suggestion, critic on this implementation

Tasks

• Improve TDT for profile #854
• Improve TDT for launch #855
• Improve TDT for campaign #856
• Improve TDT for reward #857
• Improve TDT for monitoringc #858
• Improve TDT for monitoringp #859
• Improve TDT for participation #860