bump compose-go to v2.4.7

[glours]

No description provided.

[crazy-max]

Seems something has changed with path handling?: https://github.com/docker/buildx/actions/runs/12653947166/job/35260624934?pr=2893#step:6:1351

 === Failed
=== FAIL: bake TestParseCompose (0.01s)
    compose_test.go:80: 
        	Error Trace:	D:/a/buildx/buildx/bake/compose_test.go:80
        	Error:      	Not equal: 
        	            	expected: []string{"default", "key=path/to/key"}
        	            	actual  : []string{"default", "key=path\\to\\key"}
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -2,3 +2,3 @@
        	            	  (string) (len=7) "default",
        	            	- (string) (len=15) "key=path/to/key"
        	            	+ (string) (len=15) "key=path\\to\\key"
        	            	 }
        	Test:       	TestParseCompose

=== FAIL: bake TestComposeExt (0.01s)
    compose_test.go:341: 
        	Error Trace:	D:/a/buildx/buildx/bake/compose_test.go:341
        	Error:      	Not equal: 
        	            	expected: []string{"default", "key=path/to/key", "other=path/to/otherkey"}
        	            	actual  : []string{"default", "key=path\\to\\key", "other=path/to/otherkey"}
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -2,3 +2,3 @@
        	            	  (string) (len=7) "default",
        	            	- (string) (len=15) "key=path/to/key",
        	            	+ (string) (len=15) "key=path\\to\\key",
        	            	  (string) (len=22) "other=path/to/otherkey"
        	Test:       	TestComposeExt

[crazy-max]

LGTM thanks!

About test change I will take a look if we can define the working dir when parsing the compose file as follow-up but I'm pretty sure this will break remote bake definition with local context handling.