Remove created volumes when taking down a compose stack

[andyautida14]

What does this PR do?

Cleans up orphaned volumes when taking down a Docker Compose stack.

Why is it important?

Cleaning up after your tests is important.

Related issues

• Closes [Enhancement]: Remove created volumes on "down" #644

[mdelapenya]

Thanks for this! Could you please add a test for it? 🙏

[andyautida14]

@mdelapenya just added the tests. Thanks!

[mdelapenya]

Hi @andyautida14 this will always remove the volumes. Do you think we can make it optional, creating a RemoveVolumes functional option, exactly the same as in

testcontainers-go/compose_api.go

Lines 52 to 61 in e9fa657

	// RemoveOrphans will cleanup containers that are not declared on the compose model but own the same labels
	type RemoveOrphans bool
	func (ro RemoveOrphans) applyToStackUp(o *stackUpOptions) {
	o.RemoveOrphans = bool(ro)
	}
	func (ro RemoveOrphans) applyToStackDown(o *stackDownOptions) {
	o.RemoveOrphans = bool(ro)
	}

, only for the down options?

That way users would be able to configure if they need to clean up the volumes they create

[andyautida14]

Yeah, sure. I'll try to find some time this week.

[mdelapenya]

BTW @andyautida14 please take a look at #650, which was merged after your PR: it moves the compose code to a separate module

[mdelapenya]

@andyautida14 are you still interested in this PR? We'd like to include it, although there are missing pieces regarding the functional opts and the conflicts with current code.