VMs with security groups allowing all egress traffic cannot access the Internet in 4.23.0.0

### problem

# Description

In CloudStack 4.23.0.0, a VM cannot access the Internet when its security group has egress rules configured, even when the egress rules allow all outbound traffic (0.0.0.0/0).

The same configuration works as expected in older CloudStack versions.

The issue occurs when the security group has egress rules but no ingress rules.

# Expected behavior

The VM should be able to initiate outbound connections to the Internet when the security group has an egress rule allowing all traffic.

According to the CloudStack documentation:
```
If there is no Egress rule in a Security Group, all the outgoing traffic will be allowed.
If there are Egress rules in a Security Group, only the outgoing traffic which match a Egress rule will be allowed.
Only the incoming traffic which match a Ingress rule will be allowed.
```

# Actual behavior

With CloudStack 4.23.0.0:

- The VM has a security group assigned.
- The security group has one egress rule allowing ALL outbound traffic.
- There are no ingress rules.
- The VM cannot access the Internet.

### versions

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

### The steps to reproduce the bug

1.
2.
3.
...

### What to do about it?

_No response_

Aucun fichier, test ou point d’entrée n’est identifié. Reproduisez d’abord le cas 4.23.0.0 avec un groupe de sécurité uniquement pour le trafic sortant autorisant 0.0.0.0/0, puis comparez-le à une version antérieure fonctionnelle et suivez le chemin de sortie du groupe de sécurité. Le travail est terminé lorsque la VM peut initier des connexions Internet sans aucune règle entrante et que la régression concernée est couverte par un test.

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