Feature/use protected markers for fe code validation

The ticket(https://internal-tracker.builder.ai/#/projects/3711?storyId=2008204) requests that FE code repositories start using Protected Markers(rather than Customizable Markers)from now on and should be validated against the master branch and not the approved branch (as is the case currently) going forward.

Changes have also been made to the code-validator-image at devsecops/build-images/code-validator-image!13 (merged) to support this.

Both the FE and BE pipelines will now use the script validator.py and do not require any flag to be passed in. The changes with the MR and the code-validator-image 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 separate tickets.