Py3 component tests fixes

##### ISSUE TYPE

* Improvement Request

##### COMPONENT NAME

~~~
Component tests
~~~

##### CLOUDSTACK VERSION

~~~
4.16+
~~~

##### CONFIGURATION

NA

##### OS / ENVIRONMENT

NA

##### SUMMARY

the component tests have been ported to python3 but a lot of them are non functional. In #5442 a start was made but this is going to require more work than should be stuffed in a single PR. Below is a list of the component test that need looking at. Some can be assessed and disgarded. Others should be fixed.

- [ ] test_add_remove_network.py
- [ ] test_affinity_groups_projects.py
- [ ] test_affinity_groups.py
- [ ] test_base_image_updation.py
- [ ] test_blocker_bugs.py
- [ ] test_browse_templates.py
- [ ] test_browse_volumes.py
- [ ] test_bugs.py
- [ ] test_configdrive.py
- [ ] test_dedicate_guest_vlan_ranges.py
- [ ] test_dedicate_public_ip_range.py
- [ ] test_dhcp_dns_offload.py
- [ ] test_egress_fw_rules.py
- [ ] test_escalation_listTemplateDomainAdmin.py
- [ ] test_escalations_hosts.py
- [ ] test_escalations_ipaddresses.py
- [ ] test_escalations_networks.py
- [ ] test_escalations_volumes.py
- [ ] test_escalations_vpncustomergateways.py
- [ ] test_escalation_templates.py
- [ ] test_explicit_dedication.py
- [ ] test_ha_pool_maintenance.py
- [ ] test_high_availability.py
- [ ] test_implicit_planner.py
- [ ] test_ip_resource_count_for_vpc.py
- [ ] test_multiple_public_interfaces.py
- [ ] test_organization_states.py
- [ ] test_persistent_networks.py
- [ ] test_portable_ip.py
- [ ] test_ps_resource_limits_volume.py
- [ ] test_redundant_router_cleanups.py
- [ ] test_redundant_router_deployment_planning.py
- [ ] test_redundant_router_network_rules.py
- [ ] test_redundant_router.py
- [ ] test_reset_ssh_keypair.py
- [ ] test_rootvolume_resize.py
- [ ] test_shared_networks.py
- [ ] test_snapshots.py
- [ ] test_ss_limits.py
- [ ] test_ss_max_limits.py
- [ ] test_ss_project_limits.py
- [ ] test_stopped_vm.py
- [ ] test_storage_motion.py
- [ ] test_tags.py
- [ ] test_volumes.py
- [ ] test_vpc_host_maintenance.py
- [ ] test_vpc_network_internal_lbrules.py
- [ ] test_vpc_network_pfrules.py
- [ ] test_vpc_network.py
- [ ] test_vpc_network_staticnatrule.py
- [ ] test_vpc_offerings.py
- [ ] test_vpc_routers.py
- [ ] test_vpc_vm_life_cycle.py
- [ ] test_vpc_vms_deployment.py
- [ ] test_vpn_service.py
- [ ] test_vpn_users.py
- [ ] test_vr_metadata.py
- [ ] test_zone_level_local_storage_setting.py

##### STEPS TO REPRODUCE

~~~

~~~

##### EXPECTED RESULTS

~~~

~~~

##### ACTUAL RESULTS

~~~

~~~

Commencez par l’un des fichiers de tests de composants listés, tel que test_add_remove_network.py, et examinez le comportement actuel de son portage vers Python 3. Exécutez ce test dans l’environnement de tests de composants de CloudStack, déterminez s’il doit être corrigé ou s’il peut être abandonné, puis mettez à jour la liste de contrôle une fois son comportement résolu.

Rédigé par le modèle d'indexation à partir du texte de l'issue.