Fixes for adrv9371 and adrv9009

[tagoylo]

Description

This PR includes fixes for adrv9371 and adrv9009 as well as their tests.

• adrv9371 changes includes checking if decimation is supported before setting or getting sampling frequency. It was failing on arria10 since it is not supported there.
• adrv9009 changes includes update on the obs lo attribute name. Also added new profile (got it from latest osc).

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Tested on hardware setup. arria10+adrv9371 and arria10+adrv9009

Test Configuration:

• Hardware:
• OS:

Documentation

If this is a new feature or example please mention or link any documentation. All new hardware interface classes require documentation.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have signed off all commits and they contain "Signed-off by: "
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[tagoylo]

@tfcollins PR is ready for review. I updated the emulated test workflow - to run the test without the optional dependency.

[tfcollins]

Primarily just questions on the DEC8/INT8 updates

[tfcollins]

Missing coverage flag

[tfcollins]

This applies to the other blocks that share this logic.

1. If sampling_frequency_available does not exist this will generate a strange error. Something like sampling_frequency_available is not a valid key, which won't make any sense. So there needs to be an except catch for that case
2. The case when it does but only 1 value exists doesn't really make sense or the logic flow is convoluted. If only 1 value exists then it should always return false.