The best way to customize a template file from a third-party module is to create a new theme that inherits from the parent theme and override the template file in the app/design/frontend/Custom/Theme/Vendor_Module/templates directory. This way, the customization is isolated from the original module and can be applied to a specific website or store view. Creating another layout file or a new module would not be as simple or flexible as creating a new theme. References: Frontend development guide, [Create a theme], [Theme inheritance]

To move a block from one container to another, the developer needs to use the layout instruction with the element attribute specifying the name of the block and the destination attribute specifying the name of the container. The after attribute can be used to position the block relative to other blocks in the same container. The value “-” means that the block will be placed after all other blocks, i.e., as the last child. The value “last-child” is not valid for the after attribute and will not work. The element and destination attributes should use the names of the blocks and containers, not their aliases or classes. References: [Layout instructions], [Move an element]

To completely overwrite _module.less of Orange_Checkout module in a custom theme, the developer should place the file in the Custom/theme/Orange_Checkout/web/css/source directory. This will override the default _module.less file from the Orange_Checkout module and apply the custom styles to the theme. The Custom/theme/Orange_Checkout/frontend/web/css/_module.less and Custom/theme/web/css/source/Orange_Checkout/_module.less paths are not valid and will not work, as they do not follow the theme structure or the module naming convention. References: [Theme structure], [Module naming convention]