Internal Loadbalancer fails DHCP checks and DNS checks causing Events to be flooded.

### problem

If you set up an network offering fr VPC and deploys said offering in an VPC with "InternalLBVM" as the LB service handler it appears ACS still treats it as a full VR instead of "Just" an Internal LB VM and runs the full set of tests on it. including DNS and DHCP. This causes the VM to fail health checks every 10 minutes.

We discovered this since we saw InternalLBVM was an optioon and liked the idea of having a seperate VM handling the app to DB traffic rather than sending it thrugh the already "loaded" VR for the entire VPC.

### versions

The versions of ACS, hypervisors, storage, network etc..

ACS Ver: 4.22.0
Hypervisor: KVM
Storage: Ceph
Network: Advanced with VXLAN with multicast for guest, Public, Management and storage are all Vlan based.

### The steps to reproduce the bug

1. Create a bog standard network offering for a VPC with all services enabled on VR and internal LB using Internal LBVM
2. Deploy offering on an VPC
3. Deploy the LB through the VPC - Networks - Internal LB view.
4. Attach instances to the LB so it deploys fully.
5. Watch the event log get filled up with an error every 10 minutes due to failing health checks for the LBVM

### What to do about it?

Disable DHCP and DNS health checks on any VR/Internal LB VM that is designated as only the role of an internal LB.

Aucun fichier source ni test n’est nommé. Commencez par reproduire le problème sur CloudStack 4.22.0 en suivant les étapes network-offering indiquées, puis retracez les vérifications de santé d’InternalLBVM qui génèrent les erreurs récurrentes du journal des événements. Le travail est terminé lorsque les vérifications DHCP et DNS ne s’exécutent plus pour une VM désignée uniquement comme équilibreur de charge interne, tandis que les vérifications applicables restent en place pour les autres rôles.

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