Use only protected markers for validation

https://internal-tracker.builder.ai/#/projects/3711?storyId=2008204

The main change in the MR is the removal of the use of Customizable markers. It has been decided that FE code repositories will also start using only Protected Markers from now on.

With that in mind, the following changes have also been made: Use ignore file list, so there is no switch between protected and customizable modes - to look for file in a certain location. The code now looks for the .validationignore file in a list of paths. These paths are mutually exclusive. Ruby repos will have the file in /template-app/ and FE repos will have it in /src/

Use whitelist file paths for both FE and BE repos, as they both will use the protected mode henceforth. If the file .validationwhitelist is not found, all the files in the repo will be considered for validation.

Binary files and files in /vendor/ will not be considered (this step has not been altered but will now apply for both FE and BE code validation).

There were issues seen with python 3.13 as the virtual env did not work straightaway. Hence, there has been a need to re-create the virtual env in the unit-test stage of the pipeline

Changes to the pipeline validation stage for FE and BE are part of public-tools/deploy-templates!602 (diffs)

The changes with the MR and the pipeline changes have been tested with the latest MRs on the client project here: https://gitlab.builder.ai/clientprojects/assembler_projects/prd/autobxengpro06289193-149134-react/-/merge_requests The validate job in the pipeline stage check-and-prepare performs code validation. Eg: https://gitlab.builder.ai/clientprojects/assembler_projects/prd/autobxengpro06289193-149134-react/-/jobs/92219482

https://gitlab.builder.ai/clientprojects/assembler_projects/prd/autobxengpro06289193-149134-ruby/-/merge_requests The code-validation stage in the pipeline performs code validation

The changes to the FE boiler plate code and blocks will be undertaken with seperate tickets.