feat(ui5-barcode-scanner-dialog): add 'open' property

[kgogov]

This change introduces a new open property to the ui5-barcode-scanner-dialog component, enhancing the control over the dialog's visibility. This feature aligns with the behavior of other similar components, providing a more consistent user experience.

Related: #8072

[plamenivanov91]

In the .hbs file add this to the dialog

?open="{{_open}}"

Try to add some tests with the newly added code (might simply try the method and the new prop if they get too complex for real-life flow).

[plamenivanov91]

In the .hbs file add this to the dialog

?open="{{_open}}"

Try to add some tests with the newly added code (might simply try the method and the new prop if they get too complex for real-life flow).

By the way with the code I suggested, the this.dialog.close(); and this.dialog.show(); become redundant (in BarcodeScannerDialog.ts).

[kgogov]

In the .hbs file add this to the dialog
?open="{{_open}}"
Try to add some tests with the newly added code (might simply try the method and the new prop if they get too complex for real-life flow).

By the way with the code I suggested, the this.dialog.close(); and this.dialog.show(); become redundant (in BarcodeScannerDialog.ts).

I considered your suggestion to add open attribute in the template but I've encountered the following:

• According to the sequence of actions, we need to first request permission from the user to use the camera and then decide whether to open a dialog. Actually, in our case, whether we put an open attribute in the template file is irrelevant, since we use internal methods for the purpose. I tested both cases, noticing that in the first case when we don't put an open attribute in the template, in _showDialog() we assign a dialog to this.dialog with open property set to false which is correct, but in the second case we receive a dialog with open property already set to true, which may be not correct, because technically we have not called this.dialog.show();
• I'm not so sure that we can remove the logic to show and close the internal managed dialog, because if we do we risk missing the check for user rights to use the camera.
• We also have to think about backwards compatibility.