Improved error handling when not all Interfaces are up

[romankachur-mlnx]

Description of PR

Summary:
Any test, that calls interface.yml, if encountered that some Interfaces/PortChannels are not up, will not just fail but will try to gather interfaces status from Fanout/VMs as well.

Type of change

• [] Bug fix
• Testbed and Framework(new/improvement)
• Test case(new/improvement)

Approach

How did you do it?

1. Modified interface.yml to include check_testbed_interfaces.yml,
   when 'Verify interfaces are up' step fails.
2. check_testbed_interfaces.yml will gather interfaces status on:

• DUT
• Fanout (for MLNX only, filtered by check_interfaces_status tag)
• Testbed server (by calling testbed_vm_status.yml playbook)
• relevant VMs

3. testbed_vm_status.yml palybook will connect to Testbed server and gather VMs status.
4. show_int_portchannel_status.j2 will connect to each relevant VM and gather Port-Channel status.

How did you verify/test it?

Any test that call interface.yml, in two cases:

1. Normal flow, when all interfaces are up.
   In this case nothing is changed.
2. When Fanout has deliberately its ports down,
   In that cases, the test fails as usual, but gathers Interfaces status from Fanout.
3. When some relevant VM has its Port-Channel deliberately down.
   In that cases, the test fails as usual, but gathers VMs status from Testbed server, and PortChannel status from VMs.

Any platform specific information?

Current implementation can enter Fanout switch, only if Fanout is MLNX type.
The 'Check Fanout interfaces' step in check_testbed_interfaces.yml calls fanout.yml (actually fanout role) with tag 'check_interfaces_status'
In this case anyone can modify roles/fanout/tasks/main.yml to execute Fanout specific step with
when: peer_hwsku == "<specific_fanout_type>" tags: check_interfaces_status

Example:

 ###################################################################
 # Check Fanout interfaces status                                  #
 ###################################################################
- block:
  - name: Check Fanout interfaces status
    action: apswitch template=roles/fanout/templates/mlnx_interfaces_status.j2
    connection: switch
    register: fanout_interfaces
    args:
      login: "{{ switch_login['MLNX-OS'] }}"

  - debug:
      msg: "{{ fanout_interfaces.stdout.split('\n') }}"

  when: peer_hwsku == "MLNX-OS"
  tags: check_interfaces_status

Supported testbed topology if it's a new test case?

Documentation

[chimbersaw]

@romankachur-mlnx хуйня pr переделывай