💡 Feature Request - Support Dynamic Outbound Rule Creation During Migration

## Describe the solution you'd like

Because outbound rules can only associate a single backend pool to a single front end IP address, in the situation where an external load balancer has multiple backend pools, we are not able to create a generic outbound rule that applies to all backend pool members. Currently, the module issues a warning and instructs user to manually configure outbound rules post migration.

Potential solutions:
- Distribute outbound rule allocated outbound ports across each backend pool (creating an outbound rule for each backend pool)
- Allow user to create a new backend pool with the members from all of the LB's original backend pools; create an outbound rule associating this backend pool to the first front end IP
- Allow user to map existing backend pools to front end IPs

## Describe alternatives you've considered

Current state warns user to create outbound rules post migration.

## Additional context

See #10

Examinez l’issue #10 et le chemin de migration actuel qui émet l’avertissement concernant la configuration manuelle des règles de trafic sortant. Déterminez quel comportement proposé de backend-pool et frontend-IP doit être implémenté, puis vérifiez que la migration crée les règles de trafic sortant appropriées pour plusieurs backend pools au lieu d’exiger une configuration postérieure à la migration.

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