Error statuses from dbt Cloud requests should not crash transformation tab in cloud build

[ambirdsall]

The backend forwards any not-specifically-caught error responses from dbt Cloud to the frontend; at present, these error statuses get propagated right up to the default page-wide error boundary. Since we don't control the source of these errors, we should wrap the dbt cloud transformation card component in its own error boundary, so a dbt Cloud outage or misconfigured integration doesn't prevent users from doing other transformation management.