Terraform provider - Separate resource to manage cluster routing

If we had a dedicated routing table resource in the Qovery terraform provider, we could then chain 1, 2 and 3 directly:

1. We create the cluster, and so we can get the VPC ID created by Qovery,

2. We can then create the peering connection (using the VPC ID), that will create a connection ID,

3. We can create the routing table using the connection ID.

Today, it is in the cluster. So it requires at least two deployments:

1. Deploy the cluster and the peering connection,

2. Update the code to add the routing table,

3. Re-deploy to update the cluster with the routing table.