Versions
--------
- 18.0+

Steps
-----
1. Go to eCommerce;
2. open a product page;
3. open editor;
4. toggle "Product Tags" in the CUSTOMIZE tab.

Issue
-----
Product suddenly gets displayed as not having a valid combination.

Cause
-----
PR #173823 modified the template, accidentally inserting some elements between this element:
```xml
<form t-if="product._is_add_to_cart_possible()" action="/shop/cart/update" method="POST">
```
and its consequent elements:
```xml
<p t-elif="not product.active" class="alert alert-warning">This product is no longer available.</p>
<p t-else="" class="alert alert-warning">This product has no valid combination.</p>
```

As the last of these newly introduced elements happened to include `t-if="is_view_active('website_sale.product_tags')"`, the template is still valid as far as the renderer is concerned, but obviously the display of product tags shouldn't be a prerequisite of product availability.

Solution
--------
Move the two elements back to where they make sense: right after the `product._is_add_to_cart_possible()` check.

opw-4277788

Description of the issue/feature this PR addresses:
While getting a token for Microsoft Calendar, the `_refresh_microsoft_calendar_token` method has been called without service parameters.

Current behavior before PR:
Raising an error 
```
User._refresh_microsoft_calendar_token() missing 1 required positional argument.
```
IMO, the extra parameter `service` has been added so that dynamic service can be used. 
Fixing by making service as default argument None, and if no service passed, then it will use microsoft_service (current behaviour)

```
TypeError: User._refresh_microsoft_calendar_token() missing 1 required positional argument: 'service'
  File "odoo/http.py", line 2363, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1891, in _serve_db
    return self._transactioning(
  File "odoo/http.py", line 1954, in _transactioning
    return service_model.retrying(func, env=self.env)
  File "odoo/service/model.py", line 137, in retrying
    result = func()
  File "odoo/http.py", line 1921, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2168, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 329, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 727, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/microsoft_calendar/controllers/main.py", line 45, in microsoft_calendar_sync_data
    need_refresh = request.env.user.sudo().with_context(dont_notify=True)._sync_microsoft_calendar()
  File "addons/microsoft_calendar/models/res_users.py", line 105, in _sync_microsoft_calendar
    with microsoft_calendar_token(self) as token:
  File "contextlib.py", line 137, in __enter__
    return next(self.gen)
  File "addons/microsoft_calendar/models/microsoft_sync.py", line 52, in microsoft_calendar_token
    yield user._get_microsoft_calendar_token()
  File "addons/microsoft_calendar/models/res_users.py", line 35, in _get_microsoft_calendar_token
    self._refresh_microsoft_calendar_token()

```

sentry-6026445994
OPW: 4290260

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

When the user tries to synchronize calendar with Outlook calendar,
a traceback will appear.

Traceback:
```
TypeError: User._refresh_microsoft_calendar_token() missing 1 required positional argument: 'service'
  File "odoo/http.py", line 2363, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1891, in _serve_db
    return self._transactioning(
  File "odoo/http.py", line 1954, in _transactioning
    return service_model.retrying(func, env=self.env)
  File "odoo/service/model.py", line 137, in retrying
    result = func()
  File "odoo/http.py", line 1921, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2168, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 329, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 727, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/microsoft_calendar/controllers/main.py", line 45, in microsoft_calendar_sync_data
    need_refresh = request.env.user.sudo().with_context(dont_notify=True)._sync_microsoft_calendar()
  File "addons/microsoft_calendar/models/res_users.py", line 105, in _sync_microsoft_calendar
    with microsoft_calendar_token(self) as token:
  File "contextlib.py", line 137, in __enter__
    return next(self.gen)
  File "addons/microsoft_calendar/models/microsoft_sync.py", line 52, in microsoft_calendar_token
    yield user._get_microsoft_calendar_token()
  File "addons/microsoft_calendar/models/res_users.py", line 35, in _get_microsoft_calendar_token
    self._refresh_microsoft_calendar_token()
```

https://github.com/odoo/odoo/blob/88fa5a113debfbf65f9b0862b14c15ef4da45d12/addons/microsoft_calendar/models/res_users.py#L35
Here, ``_refresh_microsoft_calendar_token`` method is called without ``service`` argument.

https://github.com/odoo/odoo/blob/88fa5a113debfbf65f9b0862b14c15ef4da45d12/addons/microsoft_calendar/models/res_users.py#L41
Here, the ``service`` argument is added but not used anywhere.

sentry-6026445994

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

When attempting to upload a file in the ``Quotation Templates`` without saving the template first, an error occurs in the terminal.

Steps to reproduce:
---
- Install the ``sale_management`` module
- Sales > Configuration > Sales Order > Quotation Templates
- Create New > Quote Builder > Click on Upload
- Try to upload a file

Traceback:
---
``ValueError: invalid literal for int() with base 10: 'false'``

Previous Behaviour:
---
When attempting to upload a file in the ``Quotation Templates`` without first saving the template, the template ID is not generated at [1]. As a result, at [2], we encounter an issue where ``int(sale_order_template_id) = 'false'``. This happens because the template tries to access its name in the uploaded file. If the template name is not available and we attempt to upload the file, ``resId`` at [1] will be returned as false.

Solution:
---
Until the template is saved, the upload button will remain hidden. Once the template is saved, the upload button will be displayed. This ensures that when a file is uploaded, the template name will be properly associated with it.

[1]- https://github.com/odoo/odoo/blob/c5ce138697d7c5ebe200566dfb8b7ba55365f100/addons/sale_pdf_quote_builder/static/src/js/quotation_document_kanban/quotation_document_kanban_widget.js#L21-L23

[2]- https://github.com/odoo/odoo/blob/c5ce138697d7c5ebe200566dfb8b7ba55365f100/addons/sale_pdf_quote_builder/controllers/quotation_document.py#L24-L26

sentry-5963406254

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This partially redoes odoo/enterprise#64900. Copying tax_ids from the sale order lines to the down payment line on the invoice doesn't work for external tax calculators. Tax percentages returned by tax calculators are only informational. When they return e.g. 5% tax, the actual amount can be different from 5% because of differences in rounding or (partial) exemptions. The authoritative tax is returned as a value amount (e.g. $10). Because of this, we cannot rely on Odoo to calculate the tax from account.tax records. It's not always going to match.

It's not possible to fix this by externally calculating taxes on the down payment invoice. The single down payment line cannot accomodate all different tax categories. Creating a down payment line per tax category (e.g. avatax_category_id) was considered, but a specific down payment product would need to be created per used tax category which would clutter the database. On top of that, down payment products are removed in later versions [1] which would complicate this approach even further.

This solves the issue by not calculating taxes on down payments at all. The down payment invoice will not be sent to external tax calculators. The resulting down payment lines on the SO won't have taxes set, and those lines will be excluded from the request to the external tax calculator. The final, "regular invoice" transaction will happen as if no down payments were made. The down payment lines won't be sent, so this will look like a regular invoice from the external calculator's view.

By default, the downpayment lines equal the subtotal of the selected down payment amount. We remove tax_ids from the lines because we cannot count on calculating tax locally (see above). To keep the behavior analogous we override the downpayment wizard to create a single down payment line with a total equal to the entered total in the wizard.

[1] odoo/odoo@9aa52dd6418e5881adc2d96d15d062b55d6150c5

opw-3971513