[FIX+IMP] rma: view permissions + portal views access errors + teams flow + Translated using Weblate (Spanish)

[FIX] rma: views permissions

Regular users don't have permissions to rma models, so we should avoid
loading views that lead to permission errors.

TT24986

rma 12.0.1.1.0

Update translation files

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: rma-12.0/rma-12.0-rma
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma/

[FIX] rma: portal views access errors

- Portal mail thread needs token config.
- Unpublished products will raise AccessError on RMAs portal views for
portal users due to record rules.
- Ensure active_id when getting actions in rma, since we could come from
a context that pollutes the expected active rma id.

[IMP] rma: teams flow

- If no RMA Team is set, we'll assign a default one to the new RMA.
- A sequence is now used to search for the top team and assign it.
- No default user is assigned when it's not in the context (i.e. portal
rmas).

[UPD] Update rma.pot

rma 12.0.1.2.0

Update translation files

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: rma-12.0/rma-12.0-rma
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma/

Translated using Weblate (Spanish)

Currently translated at 96.2% (253 of 263 strings)

Translation: rma-12.0/rma-12.0-rma
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma/es/

rma/static/description/index.html

@@ -440,8 +440,29 @@ stock location and click on ‘Return’ button.</li>
 Every RMA will be in confirmed state and they will
 be linked to the returning operation generated previously.</li>
 </ol>
-<p><strong>Note: An RMA can also be created from an incoming email (See configuration
-section).</strong></p>
+<p>There are Optional RMA Teams that can be used for:</p>
+<blockquote>
+<ul class="simple">
+<li>Organize RMAs in sections.</li>
+<li>Subscribe users to notifications.</li>
+<li>Create RMAs from incoming mail to special aliases (See configuration
+section).</li>
+</ul>
+</blockquote>
+<p>To create an RMA Team (RMA Responsible user level required):</p>
+<blockquote>
+<ol class="arabic simple">
+<li>Go to <em>RMA &gt; Configuration &gt; RMA Teams</em></li>
+<li>Create a new team and assign a name, a responsible and members.</li>
+<li>Subscribe users to notifications, that can be of these subtypes:<ul>
+<li>RMA draft. When a new RMA is created.</li>
+<li>Notes, Debates, Activities. As in standard Odoo.</li>
+</ul>
+</li>
+<li>In the list view, use the cross handle to sort RMA Teams. The top team
+will be the default one if no team is set.</li>
+</ol>
+</blockquote>
 </div>
 <div class="section" id="known-issues-roadmap">
 <h1><a class="toc-backref" href="#id3">Known issues / Roadmap</a></h1>