AMD VIP agent abstractization

[IstvanZsSzekely]

PR Description

VIP agents AMD are parameterized are all parameterized agents and they don't have an abstract parent class. This forces us to use Environments which are also parameterized, so the AMD agents can be instantiated inside the environment.
The ADI VIP classes encapsulate the AMD VIPs, which allows us to create VIP agents in a cleaner way, including our own sequencers and monitors, but these are also parameterized. Our VIP classes have an abstract parent class, which means polymorphism works on them.
This PR adds a workaround for this issue to have an abstract, polymorphic environment, that can use VIPs in multiple modes without the need of redefining the entire environment multiple times with different modes. This polymorphic attribute is set at environment creation, which gives a seamless plug-and-play feature when multiple environments need to be connected for a more comprehensive system level testbenches.
To be reviewed after #165

PR Type

• Bug fix (change that fixes an issue)
• New feature (change that adds new functionality)
• New test (change that adds new test program and/or testbench)
• Breaking change (has dependencies in other repositories/testbenches)
• Documentation (change that adds or modifies documentation)

PR Checklist

• I have followed the code style guidelines
• I have performed a self-review of changes
• I have ran all testbenches affected by this PR
• I have commented my code, at least hard-to-understand parts
• I have signed off all commits from this PR
• I have updated the documentation (wiki pages, ReadMe files, Copyright etc)
• I have not introduced new Warnings/Errors on compilation/elaboration/simulation
• I have set the verbosity level to none for the test program

[IstvanZsSzekely]

Ran a CI build on the branch, fixed issues that are related to these changes.

[IstvanZsSzekely]

Re-ran the CI build on the branch, everything works the same way it currently does on main.

[LBFFilho]

A bit of cosmetics with the .this usage.
This is a bit nitpicky, so feel free to ignore.

I've illustrated it with m_axis_sequencer.sv, but it also applies to other classes on the PR

[IstvanZsSzekely]

A bit of cosmetics with the .this usage. This is a bit nitpicky, so feel free to ignore.

I've illustrated it with m_axis_sequencer.sv, but it also applies to other classes on the PR

This is something that became apparent to me as well, while working on some other features. It's not just these files that are affected, but many others. I would propose to postpone this to a future development branch, where we go over all and update everything in one go.