Fix the rewrite map config template to render the routing config in correct order

We had an issue where the user acessing the OOD in knightly env on the GPFS5 side is being routed to the GPFS4 side. The problem stemmed from incorrect configuration ordering in the rewrite map config /var/www/rewrite_map_config.py, which was fixed by properly defining the target groups' order in the pipeline's extra_vars variable. The default group, hostname key-value pair, should be the last one in the order.

Rewrite the template logic in the rewritemap_config.j2 ansible template https://gitlab.rc.uab.edu/rc/hpc-factory/-/blob/main/ansible/roles/rewrite_map/templates/rewrite_map_config_py.j2?ref_type=heads#L2 to be sensitive to the default flag in the target groups configuration.

We need to provide a fix so that a user can define the target_groups configuration value in any order but the default value should be rendered last.