[ADD] util/update_table_from_dict

[Pirols]

A recurrent challenge in writing upgrade scripts is that of updating values in a table based on some form of already available mapping from the id (or another identifier) to the new value, this is often addressed with an iterative solution in the form:

for key, value in mapping.items():
    cr.execute(
        """
        UPDATE table
           SET col = %s
         WHERE key_col = %s
        """,
        [value, key],
    )

or in a more efficient (only issuing a single query) but hacky way:

cr.execute(
    """
    UPDATE table
       SET col = (%s::jsonb)->>(key_col::text)
     WHERE key_col = ANY(%s)
    """,
    [json.dumps(mapping), list(mapping)],
)

With the former being ineffective for big mappings and the latter often requiring some comments at review time to get it right. This commit introduces a util meant to make it easier to efficiently perform such updates.

[robodoo]

[Pirols]

Usage example: https://github.com/odoo/upgrade/pull/8079

[KangOl]

upgradeci retry with always only base

[aj-fuentes]

I think the interface should be

Suggested change

	def update_table_from_dict(cr, table, mapping, key_col="id", bucket_size=DEFAULT_BUCKET_SIZE):
	def update_table_from_dict(cr, table, columns, mapping, key_col="id", bucket_size=DEFAULT_BUCKET_SIZE):

From experience, when we use a dict to update, sometimes the dict becomes too big. If we make the keys repeated each time we may unintentionally make this harder. We can instead take a mapping {id: [val1, val2,...]} and a spec of columns to update [col1, col2, ...], or {id: val} with just col1. This has the advantage that for the most common case where we update a single column the values could be scalar as well. When columns is a list then the values in the mapping must be a list as well.
Example usage:

update_table_from_dict(cr, table, "name", {1: "foo", 2: "bar"})
update_table_from_dict(cr, table, ["name", "passwd"], {1: ["foo", "baz"], 2: ["bar", ""]})