Use symfony/yaml, new Soketi service, and new sail:add command

[tonysm]

Changed

• Adds the symfony/yaml dependency to ease Yaml manipulation (there are some differences to the generated Yaml file, I'll try to describe them below)
• Extracted some of the InstallCommand methods into a InteractsWithDockerComposeServices concern (trait). I needed those methods in the new sail:add command.

Add

• Adds a new artisan sail:add command that we can use to add new services to our Sail setup. We're currently expecting this command to run from the host machine (since it uses some docker commands in the prepareInstallation method). I think the sail:install command also has the same expectation (I've always ran it from my host machine)
• Adds a new soketi service to ease broadcasting setup on Sail

---

There are some changes to the Yaml generated by the symfony/yaml package, especially around sequences. One example is the Redis health-check command:

Before:

services:
    # ...
    redis:
        # ...
        healthcheck:
            test: ["CMD", "redis-cli", "ping"]

After:

services:
    # ...
    redis:
        # ...
        healthcheck:
            test:
                - CMD
                - redis-cli
                - ping

Both versions work the same, I guess it's just aesthetics (I prefer the before). Couldn't find a way to change it (maybe we could do some string manipulation as before?)

I explored adding a sail add command to the bin/sail script, but not sure. The script would need a few changes, 'cause we can run php artisan sail:add inside the container but we'd need to run the docker commands from the host machine (unless we share the docker socket with the container and install docker in the laravel.test, this way I believe we could run the prepareInstallation method inside the container as well).

Why not use the artisan sail:install to add the new dependencies?

That's what I've been using. But I always had to list all services I wanted to keep + the new service. Even though the new sail:add command and the sail:install command are technically the same now (after the changes here), the add one passes the intention of addition. But I guess it's not necessary.

---

This is all a proof of concept. Wasn't sure where to suggest the sail:add feature, but the GH workflow said to open a PR. Happy to open separate PRs in case y'all don't want to add an extra dependency, or don't want to add soketi, etc.

[taylorotwell]

Hey @tonysm - this PR has some conflicts. Please mark as ready for review when those are resolved.

[tonysm]

@taylorotwell I've rebased it. By the way, I only opened this as a discussion starter. No pressure to merge it. Happy to open separate PRs for each of the changes I described here or to pick only the wanted pieces 👍🏼

[taylorotwell]

@tonysm this all looks pretty good to me. I'm ready to merge it in if you are.

[tonysm]

Alright 👍

[driesvints]

Thanks @tonysm!