Refactor(eos_cli_config_gen): Rearrange generated CLI for traffic-policies, system and static-routes

[MaheshGSLAB]

Change Summary

Rearrange generated CLI for traffic-policies, system and static-routes.

Related Issue(s)

Fixes #

Component(s) name

arista.avd.eos_cli_config_gen

Proposed changes

Rearrange generated CLI for traffic-policies, system and static-routes to match with actual EOS

How to test

Run molecule

Checklist

User Checklist

• N/A

Repository Checklist

• My code has been rebased from devel before I start
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation and documentation have been updated accordingly.
• I have updated molecule CI testing accordingly. (check the box if not applicable)

[github-actions]

Review docs on Read the Docs

To test this pull request:

# Create virtual environment for this testing below the current directory
python -m venv test-avd-pr-4590
# Activate the virtual environment
source test-avd-pr-4590/bin/activate
# Install all requirements including PyAVD
pip install "pyavd[ansible] @ git+https://github.com/MaheshGSLAB/ansible-avd.git@eos-sort-part-8#subdirectory=python-avd" --force
# Point Ansible collections path to the Python virtual environment
export ANSIBLE_COLLECTIONS_PATH=$VIRTUAL_ENV/ansible_collections
# Install Ansible collection
ansible-galaxy collection install git+https://github.com/MaheshGSLAB/ansible-avd.git#/ansible_collections/arista/avd/,eos-sort-part-8 --force
# Optional: Install AVD examples
cd test-avd-pr-4590
ansible-playbook arista.avd.install_examples

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[Shivani-gslab]

In running config, the command reflects like - ip access-group acl4_3 in, if vrf is default. Also, vrf could be default for any one access_group.
I know, this PR is for ordering only, just noting down here for future enhancements.
@ClausHolbechArista @gmuloc @MaheshGSLAB

[gmuloc]

yes I am not sure we can capture this except if we remove the capability not to supply a VRF. I have merged the PR knowing this we can track it in an issue maybe