Assert SDK version is consistent in the CLI generation process

[shreyas-goenka]

Changes

Followup from #1809 (comment). User will see the following error if the SDK version does not match during CLI code generation.

--- FAIL: TestConsistentDatabricksSdkVersion (1.34s)
    info_test.go:53: 
                Error Trace:    /Users/shreyas.goenka/cli/internal/build/info_test.go:53
                Error:          Not equal: 
                                expected: "0c86ea6dbd9a730c24ff0d4e509603e476955ac5"
                                actual  : "6f6b1371e640f2dfeba72d365ac566368656f6b6"
                            
                                Diff:
                                --- Expected
                                +++ Actual
                                @@ -1 +1 @@
                                -0c86ea6dbd9a730c24ff0d4e509603e476955ac5
                                +6f6b1371e640f2dfeba72d365ac566368656f6b6
                Test:           TestConsistentDatabricksSdkVersion
                Messages:       please update the SDK version before generating the CLI

Tests

Manually asserted that:

1. Generating the CLI without the SDK bump causes an error.
2. Generating the CLI after the SDK bump works as expected.
3. The test works even when the SDK is pinned to a specific commit like v0.47.1-0.20241002195128-6cecc224cbf7

[pietern]

Can you figure out how we can not run this test by default?

Maybe with build tags or something.

[shreyas-goenka]

@pietern I think we can skip a filter on this test for now. It's pretty fast, it ran 100 times in 3.7 seconds on my local machine.

It's difficult to determine whether we are regenerating the CLI in the context of the CLI code itself. The build tags are only set in the release workflow. We'd probably need to create some sort of flag in the push.yml workflow to note when a PR is regenerating the CLI.