Back in 2018ish when this logic was written BigQuery did not have a DDL syntax for updating the table description. They do now so we should take advantage of it as it will be more performant and more stable.
More performant because our current logic requires two calls: one to get the current table state the other to update it while using the ddl would only require a single call. More stable because it would fix the edge case where an update fails because a concurrent call updated the table in between the get/update calls.
See bigquery__alter_relation_comment code.