Add `include` option for `supabase start`

Currently, there's an option to exclude containers from supabase start. This is very useful for CI, as if you just need to run pgTAP tests against the database, you can use the Supabase CLI in CI to set up the container.

However, when new container types are added, they need to also be excluded. This has caused CI to break for us as newer containers were dependent on older containers which were being excluded.

I'd like to see a -i or --include option for supabase start which does the opposite of the -x flag and allows you to only start the specified containers. Of course, the two flags would have to be mutually exclusive. This makes use of supabase start more resilient to the issues caused by updates that I mentioned earlier.

In my head, you might have something like the following: