context list: remove temporary ContextType from JSON output

[thaJeztah]

• relates to context list: temporarily add ContextType to JSON output #5094

This reverts commit fed9fa0.

This removes the ContextType field, which was temporarily added to provide compatibility with the "compose-cli" wrapper that shipped with Docker Desktop. The compose-cli wrapper extended the context struct with an additional field that was not part of the CLI itself, but was used by Visual Studio to detect the type of context.

This temporary field shipped as part of Docker 27.0 June 2024), which should be enough time for Visual Studio to have adjusted their integration.

- Human readable description for the release notes

Go SDK: cli/command/context: remove temporary `ContextType` field from JSON output

- A picture of a cute animal (not mandatory but encouraged)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 59.11%. Comparing base (3349492) to head (cda7235).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5981      +/-   ##
==========================================
- Coverage   59.12%   59.11%   -0.01%     
==========================================
  Files         355      355              
  Lines       29740    29716      -24     
==========================================
- Hits        17583    17567      -16     
+ Misses      11182    11174       -8     
  Partials      975      975              

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[thaJeztah]

Interesting failure; some issue with that test? Looks like potentially the context would be cancelled, which closes the pipe?

cli/cli/command/container/run_test.go

Lines 248 to 252 in 3349492

	case <-ctx.Done():
	assert.NilError(t, server.Close(), "failed to close imageCreateFunc server")
	return
	default:
	assert.NilError(t, enc.Encode(jsonmessage.JSONMessage{

65.88 === FAIL: cli/command/container TestRunPullTermination (0.00s)
65.88     run_test.go:252: assertion failed: error is not nil: io: read/write on closed pipe

[thaJeztah]

Flaky test;

2.78 === FAIL: cli/command/network TestNetworkPrunePromptTermination (0.01s)
62.78     prune_test.go:27: assertion failed: error is "network prune cancelled has been cancelled" (errdefs.errCancelled), not "prompt terminated" (command.ErrPromptTerminated errdefs.errCancelled)

And weird error: "network prune cancelled has been cancelled"; I suspect the weird error message was accidental;

cli/cli/command/network/prune.go

Line 60 in 3349492

return "", errdefs.Cancelled(errors.New("network prune cancelled has been cancelled"))

Looks like it was updated in 7c722c0