[FIX] base: consider multi_edit="1" views editable

[beledouxdenis]

Since #95729

nodes with a groups= are completely removed from the views when
the user is not part of the group, instead of being made invisible.

In that PR, views have been adapted to add back fields, with invisible="1",
when they were required, for instance when they were used in a domain
of another field which was still there despite the user is not part
of the given group.

As tree views having multi_edit="1" where not considered
as editable views, the domain of fields in these views were not
validated:

• odoo/odoo/addons/base/models/ir_ui_view.py

  Line 1460 in 1fb8fa1

  or node_info['editable'] and field._description_domain(self.env)

• odoo/odoo/addons/base/models/ir_ui_view.py

  Lines 1321 to 1322 in 1fb8fa1

  	def _editable_tag_tree(self, node, name_manager):
  	return node.get('editable')

while they are well required for the web client,
in multi_edit="1" this is possible to edit relational/many2one field,
and therefore it will do name_search calls using the domain of the
field, and therefore the fields used in these domains must always
be present in the views. Without it, a crash in the web client occurs
when attempting to edit the relational/many2one field.

This revision targets to consider the multi_edit="1" tree views
as editable, to make the field domains validated as they should be.

Hence, views are adapted to add back fields with invisible="1"
when they are required in domains of other fields.

[robodoo]

Pull request status dashboard.

[pedrobaeza]

@moylop260 the Denis' initial explanation is what we are handling in OCA/odoo-pre-commit-hooks#10

[beledouxdenis]

robodoo rebase-ff
robodoo r+

[robodoo]

Merge method set to rebase and fast-forward.