Replace capirca dependency with aerleon

[sdoiron0330]

Closes #236

What's Changed

Removed capirca from dependencies
Added aerleon as a dependency
Replaced all references of capirca with aerleon

[jdrew82]

@sdoiron0330 I'm pretty sure this would be a breaking change. What's the impetus behind switching to Aerleon?

[sdoiron0330]

capirca has had an open vulnerability for not using yaml.safe_load as they parse those files. honestly, it's unclear to me if they've actually fixed that vulnerability or if they just haven't properly documented that it's been fixed. either way, the code scanners that my customer is using says that capirca is not allowed due to said vulnerability. aerleon was discussed as a potential swap as it is a fork of capirca that looks to have been created because of the difficulty to move things forward in capirca

[jdrew82]

@sdoiron0330 apologies for the lack of response to this since last year. At this point it appears that you need to rebase this PR against the develop branch to resolve the conflicts we're currently seeing. As for the change to Aerleon, I'm happy to continue considering it but I will warn that I'm working on refactoring these models to extend their usage outside the current layer 7 firewall policy focus.

[loulecrivain]

@sdoiron0330 @jdrew82 what's the status on this PR?
We (WDZ GmbH) have new firewall support (Fortinet and Proxmox) landing in Aerleon. That'd be nice to have in Nautobot too 😊

I'd be happy to pick up where you left off and/or make a new PR if needed.

[jdrew82]

We need this rebased so the conflicts are resolved. Then I can continue my review.

[loulecrivain]

Ok I see. I'll make a new PR on my end and will ask you for a review when it's done. Thanks!

[jdrew82]

@loulecrivain Is this related to #308 or should this be closed?

[loulecrivain]

You can close it, #308 replaces it