Spin Command trigger should not terminate host when multiple triggers are defined

[ThorstenHans]

I created a Spin App with two triggers:

# ...

[[trigger.http]]
route = "/..."
component = "api"

[[trigger.command]]
component = "cleanup"

# ...

Actual Behavior

Upon starting the app with spin up, the cleanup component is invoked. Once the component finished processing, the spin up process is terminated.

Expected Behavior

The spin up host process should stay alive once the cleanup component has finished processing

[karthik2804]

This is more the behavior of spin itself and the trigger plays no part in it.
ref: spinframework/spin#2419
also #7 (comment)