The aim of this commit is improving the design of external value in accounting reports.

Before this commit, user has to click on the pencil/edit icon to open a popover to allow him to edit the value. Once the value edited, the user still has to "Post" the value by validating it via a button.

Now, the user can edit the value in place (no more popover) and the value is automatically saved when we leave the focus on the field.

This commit also introduces an easier way to edit the boolean figure_type for external value.
Before this commit, still in the popover, the user has to choose between 2 radio buttons (Yes / No).
Now, it's easily editable by clicking on the value or on the pencil / edit icon.

Finally, this commit introduces the possibility to have editable date or datetime figure_type. To do that, we are using the hook useDateTimePicker which allows us to custom the behavior of the DateTimePicker.

To achieve this transformation, we decided to separate the logic in 4 different components.
- AccountReportLineCellEditable: which is the component you have to call when you want to allow an external value editable. This is the conductor of how things should work.
- AccountReportLineCellEditableBoolean: To easily handle boolean figure_type.
- AccountReportLineCellEditableDateTime: To easily handle date and datetime figure_type.
- AccountReportLineCellEditableLiteral: To easily handle integer, string, float and monetary figure_type.
NB: This component doesn't have the best name for it, but it's to avoid one component per figure_type.

no task id

*: stock_barcode, stock_barcode_picking_batch

- Currently, in the `Barcode App` tab under `Manufacturing operation` type, certain settings such as `Destination location`, `Force destination for all products`,  `Group batch lines` and `Move Entire Packages` have no impact in MO and can be made invisible, as their lack of effect may confuse users about their usage.

- `Source location` and `lot/serial` scan validations were incorrectly applied to `by-products`, which are produced at `Production location` and don't require such scanning. This made by-product lines non-editable in the barcode, reducing usability for byproduct processing. Barcode interface for by-products lacked automatic lot generation, requiring users to manually create the next available lot, resulting in a slower and less efficient process.

- Also, if a line has a reserved lot from the backend and another existing lot is scanned, it is applied correctly. However, when a `new lot/serial` is scanned even with `use_create_components_lots` enabled, the system falls back to the originally reserved lot from the backend, which leads to incorrect behavior. With this change, scanning a new lot clears the existing reserved lot and applies the scanned value instead. This ensures accurate lot assignment, improving traceability and reliability during barcode operations.

These changes hides irrelevant settings for MRP operations, refines the field label `(Product → Component)` specifically for mrp operations, prevents incorrect `source location` and `lot/serial scan` validations from affecting `by-product lines`, and adds direct `lot generation` for by-products in the barcode screen , and ensure that generated or scanned lot names are visible in the MRP form view, as the previous compute logic was always hiding the lot name even when it was set. These updates reduce confusion and make the mrp barcode workflow smoother and more efficient, especially for by-products.

TaskID-4655907