refactor gomega assertions

[mayankshah1607]

Problem

Currently, we're making use of Gomega as a matcher library with Ginkgo, for making assertions in the tests. An example of such an assertion would be:

func testSomething() {
    err := doSomething()
    gomega.Expect(err).Should(gomega.BeNil(), fmt.Sprint("failed to do something: %s", err.Error()))
}

The problem with using these directly in the tests would be that contributors now have to deal with learning the Gomega syntax for assertions, and also having too many of these look ugly and make the code less readable.

Solution

We could create reusable helper functions that essentially act as wrappers around these assertions. For example

func ExpectNil(item interface{}. annotation string) {
    gomega.Expect(err).Should(gomega.BeNil(), message)
}

func testSomething() {
    err := doSomething()
    utils.ExpectNil(err, fmt.Sprintf("failed to do something: %s", err.Error()))
}