[FIX] util.move_model: add version check for email.template

[MrRose765]

In this PR, the email_template update line was preventing people from creating an email.template custom model even though it is not used in standard since version 8.

Related issues :

• PR-specific
• OPW-6055415

[robodoo]

[aj-fuentes]

The rename happens in 8.saas~6.1 (weird old versioning scheme). Thus when Odoo 9.0 is running it can still encounter it.
https://github.com/odoo/upgrade/blob/9d12694ed46d478492ad43611b284c754ae69ce6/migrations/mail/8.saas~6.1.0/pre-adapt-models.py#L5

Suggested change

	if version_gte("9.0"):
	update_imd("mail.template", path="model")
	else:
	update_imd("email.template", path="model")
	update_imd("mail.template" if version_gte("10.0") else "email.template", path="model")

[MrRose765]

In that case, wouldn't it be a problem for the upgrade scripts that call move_model in 9.* ? (In other words, after the rename but before 10.0)

Example : https://github.com/odoo/upgrade/blob/94b2c0207acb488ec68cdad65884e05773b8dab1/migrations/account_extra_reports/9.0.1.1/pre-get-from-account.py#L5

[aj-fuentes]

There is no perfect solution. When Odoo 9 is running both models could appear --before or after the rename. We could do as well:

    if not version_gte("10.0"):
        update_imd("mail.template", path="model")  # renamed in 8.saas~6.1
    update_imd("email.template", path="model")

This could cause issues if email.template was used in a DB in 8.0, but we get every few such upgrades nowadays, and they need other specific fixes anyway.

[KangOl]

upgradeci retry with always only mail in all versions

[KangOl]

upgradeci retry with always only account crm im_chat in 9.0 master