[Enhancement]: Expose the compose recreate options

[rach-id]

Proposal

Currently, the implementation uses by default the "diverged" recreate strategy for docker-compose setups, and doesn't provide a way to override that:

testcontainers-go/modules/compose/compose_api.go

Lines 194 to 195 in bc15b11

	Recreate: api.RecreateDiverged,
	RecreateDependencies: api.RecreateDiverged,

Does it make sense to also provide these as options?

The issue I am facing is when trying to start the compose setup incrementally, i.e. start a container, run some tests, start another container that uses the first one as a dependency and run some other tests. This gives me the following errors:

• if I specify the container dependencies as part of RunServices (deps), it fails with The container name "..." is already in use by container
• If I dont, I get the no such service: ... error

So, I guess if we have the Recreate and RecreateDependencies options exposed, that would help with this, and also allow for more flexible testing setups.

[mdelapenya]

Hey @sweexordious thanks for opening this issue. I'm currently triaging the repo, focusing on compose stuff.

I think you could achieve it if we exposed the stackUpOptionFunc and stackUpOptions types:

import tccompose "github.com/testcontainers/testcontainers-go/modules/compose"
...

	recreateForceFn := func() tccompose.StackUpOption {
		// At this moment, the types are not exported: 
		// return tccompose.stackUpOptionFunc(func(o *tccompose.stackUpOptions) {
		return tccompose.StackUpOptionFunc(func(o *tccompose.StackUpOptions) {
			o.Recreate = api.RecreateForce
			o.RecreateDependencies = api.RecreateForce
		})
	}

Then you would be able to define your own recreation strategy.

I only need to think about the implications of exposing the type, as this module was added long time ago and I'm not that familiar with it as I'd like to.