This commit improves the layout of quantity buttons in barcode in both cases of physical inventory and transfers.

### Before this commit:
1- The fulfill button disappeared if `quantity done == demand - 1` which causes the increment and decrement buttons to shift their positions, that caused confusion to the user.

2- The delete button (red trash button) in case of physical inventory count was used to set the count of the product to 0 and remove the line from barcode view.

3- The "?" button (to mark the quantity as not set yet while inventory count) appeared whether the quantity on line was set to a number >= 0.

4- The button for registering components was among the lower buttons (increment, decrement, and fulfill).

### After this commit:
1- The fulfill button still disappears when `quantity done == demand - 1` but an empty spacer replaces it, which causes other buttons to hold positions.

2- The delete button now only appears when the user adds a product by themselves using the form or scanning the product (not while the product is in an inventory request). Also the functionality is of the button is now different, it just removes the line from the barcode view without affecting the inventory count at all.

3- The "?" button now only appears if the quantity = 0.

4- The button for registering components is no next to the edit button.

Upgrade PR: https://github.com/odoo/upgrade/pull/10224
Task-6095725

see: https://github.com/odoo/odoo/pull/252766

ERROR: Subtest TestAiCrmLivechatTools.test_create_lead_tool_from_livechat (login='public_user') Traceback (most recent call last):
  File "/data/build/odoo/odoo/tools/safe_eval/evaluation.py", line 431, in safe_eval
    return unsafe_eval(c, globals_dict, None)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "ir.actions.server(272,)", line 1, in <module>
  File "/data/build/odoo/odoo/tools/safe_eval/runtime.py", line 659, in safe_call
    return callee(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/enterprise/ai_crm/models/crm_lead.py", line 16, in _ai_create_lead
    self.create(self._ai_prepare_lead_creation_values({
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/build/enterprise/ai_crm_livechat/models/crm_lead.py", line 21, in _ai_prepare_lead_creation_values
    if 'website' in self.env and (visitor := channel.livechat_visitor_id):
                                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'discuss.channel' object has no attribute 'livechat_visitor_id'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/data/build/odoo/odoo/tests/common.py", line 2949, in with_users
    func(self, *args, **kwargs)
  File "/data/build/enterprise/ai_crm_livechat/tests/test_ai_crm_livechat_tools.py", line 17, in test_create_lead_tool_from_livechat
    tool.with_context({'discuss_channel': livechat_channel})._ai_tool_run(None, {
  File "/data/build/enterprise/ai/models/ir_actions_server.py", line 288, in _ai_tool_run
    self._run_action_code_multi(eval_context=eval_context)
  File "/data/build/odoo/odoo/addons/base/models/ir_actions.py", line 1012, in _run_action_code_multi
    safe_eval(self.code.strip(), eval_context, mode="exec", filename=str(self))
  File "/data/build/odoo/odoo/tools/safe_eval/evaluation.py", line 437, in safe_eval
    raise ValueError('%r while evaluating\n%r' % (e, expr))
ValueError: AttributeError("'discuss.channel' object has no attribute 'livechat_visitor_id'") while evaluating "ai['result'] = record.sudo()._ai_create_lead(name, contact_name, description, email, phone, team_id, tag_ids, priority, country_id, state_id, city, zip_code, street, job_position)"

Steps to reproduce:
-
1. Install `website` and `planning_field_service` (so `website_planning_field_service` auto-installs).
2. Open Settings and click Save.

Issue:
-
An "Uninstall modules" wizard pops up offering to remove `website_planning_field_service`.

Cause:
-
Since the module is now `auto_install` with its `post_init_hook` removed, it is installed alongside `website` and
`planning_field_service` while the setting remains disabled by default.

On Save, `set_values` re-derives the `module_website_planning_field_service` field from a company `search_count`, setting it to False when no company has the feature enabled, even though the module is installed. Base `execute()` then sees `module_* = False` on an installed module and re-offers the uninstalls.

Fix:
-
Make `set_values` install-only: enabling the setting still installs the module, but disabling it no longer attempts to uninstall it. The module is now also used to show or hide Field Service information in the portal, so it must remain installed even when the Website Form feature is disabled.

task-6330718

Version:
- 19.0

Steps to reproduce:
- Create a sign template with a readonly sign item linked to an auto field.
- Use a reference record where the linked field value is empty or False.
- Send the document for signing.
- Complete the signing flow.

Issue:
- Readonly sign items linked to auto-filled values could not properly handle
  falsy values. Empty values could trigger the error "Some required items are
  not filled" and completed sign requests displayed the sign item placeholder
  instead of the actual auto-filled value.
- completed document generation could fail when rendering falsy values for
  textarea sign items.

Cause:
- Falsy auto-filled values were ignored during constant item population and
  replaced by the sign item placeholder. Additionally, readonly constant items
  were included in required field validation and completed sign requests
  continued to display placeholders when the stored value was empty.
- document rendering assumed sign item values were always strings for textarea
  sign items but when auto field is empty it value can be False.

Fix:
- Preserve falsy values when populating readonly constant items, exclude
  constant items from signer validation, and hide placeholders for empty
  auto-filled constant items when displaying completed sign requests.
- Normalize falsy values to prevent crashes and allow completed documents
  to be generated correctly.

Forward-Port-Of: odoo/enterprise#121299
Forward-Port-Of: odoo/enterprise#121009