The system will crash with an error when we `fetch transactions` and then click on the total amount in the top right corner, because the method `action_open_bank_balance_in_gl` expects `exactly one journal record` (self.ensure_one()), but receives an empty recordset.

**Steps to Produce:-**

1. Install the `Accounting` module.
2. Navigate to `Invoicing > Bank`, then click on "Search Banks" and connect with the `Odoo Bank Sync Demo`.
3. Click on `Fetch Transactions` and wait for the process to complete.
4. In the new view, click on the `total amount` located in the `top right corner`.

**Error:-**
`ValueError: Expected singleton: account.journal()`

**Solution:-**
- At [1], in `default_context` we can see that `active_id` is not given.

 [1] https://github.com/odoo/enterprise/blob/4b8edc19dbece15f7843ec3647c464307e165906/account_online_synchronization/models/account_online.py#L878-L882

- So, in this commit now active_id is added in default_context to prevent the error

**Sentry - 6644825437**

If customers migrate to version 18 from a lower version, 'Create Bill' record newly introduced so it just create but not translated.

**Before fix:**
```
test_18=# select id,name from account_reconcile_model;
 id |                                                            name                                                            
----+----------------------------------------------------------------------------------------------------------------------------
  3 | {"en_US": "Line with Bank Fees", "es_AR": "Línea con comisiones bancarias"}
  1 | {"en_US": "Invoices/Bills Perfect Match", "es_AR": "Coincidencia perfecta de facturas"}
  2 | {"en_US": "Invoices/Bills Partial Match if Underpaid", "es_AR": "Coincidencia parcial si hay pagos parciales en facturas"}
  4 | {"en_US": "Create Bill"}
  5 | {"en_US": "Internal Transfers", "es_AR": "Transferencias internas"}
```

**After Fix:**
```
test_18=# select id,name from account_reconcile_model;
 id |                                                            name                                                            
----+----------------------------------------------------------------------------------------------------------------------------
  1 | {"en_US": "Invoices/Bills Perfect Match", "es_AR": "Coincidencia perfecta de facturas"}
  2 | {"en_US": "Invoices/Bills Partial Match if Underpaid", "es_AR": "Coincidencia parcial si hay pagos parciales en facturas"}
  5 | {"en_US": "Internal Transfers", "es_AR": "Transferencias internas"}
  3 | {"en_US": "Line with Bank Fees", "es_AR": "Línea con comisiones bancarias"}
  4 | {"en_US": "Create Bill", "es_AR": "Crear factura"}
```
Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Steps:
------
- Install `l10n_fr_pos_cert`
- Open a PoS session, and add a combo product, orderlines corresponding to the combo procuts will be added
- Hide the numpad by clicking on the selected orderline.
- Choose a random orderline, and click on the text "Old unit price"

-> Observe that the numpad will appear and then disappear immediately.

Reason:
-------
When clicking the text "Old unit price", two click events are dispatched, those running the click handler twice, the first time it selects the orderline and hence show the numpad, and the second time, it unselects that same orderline, hiding the numpad.

Fix:
----
We disable the pointer-events on the "Old unit price" text, making it unclickable, more precisely, preventing it from being a `target` of a click event. With that change, the click handler (aka `clickLink` [1]) will only run once.

[1]: https://github.com/odoo/odoo/blob/8fb7e5fd304697aebcce085602a5f3a1ecaf757a/addons/point_of_sale/static/src/app/screens/product_screen/order_summary/order_summary.xml#L9

opw-4636261

_Description of the issue/feature this PR addresses:_

When setting up a new activity template on a new activity plan, HR specific values for 'Assignment' such as Coach or Manager are not available.

_Current behavior before PR:_

As an HR manager, go to menu HR -> Configuration -> Activity Plan. Click 'New'. Under Activities To Create, click 'Add a line'. Under 'Assignment', the only options available are Ask at launch and Default user.

<img src="https://github.com/user-attachments/assets/97be6790-b450-42c6-910a-07483c30e175" width=50% height=50%>

Cancel the 'Create Activities' popup. Give the plan a name and save it. Again, under Activities To Create, click 'Add a line'. Only now are HR specific options (Coach, Manager etc) available under 'Assignment'.

_Desired behavior after PR is merged:_

HR specific values for 'Assignment' are immediately availalbe when setting up a new plan for the Employee model.

![image](https://github.com/user-attachments/assets/391da1c1-c1ed-495a-a25f-48941554791a)

_Technical solution:_

Pass the plan's model as the default model for new templates so that the related field is populated with a value that unlocks the HR specific values before first saving the plan.

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