Add support for setting router pim sparse-mode ssm range

[quulah]

Change Summary

Types of changes

• 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 change)
• Code style update (formatting, renaming)
• Refactoring (no functional changes)
• Documentation content changes
• Other (please describe):

Related Issue(s)

Related to #979

Component(s) name

arista.avd.eos_cli_config_gen

Proposed changes

• Add supports for specifying ssm range parameter on router pim

How to test

Checklist:

• My code has been rebased from devel before I start
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have updated molecule CI testing accordingly
• All new and existing tests passed (pre-commit, make linting and make sanity-lint).

[onurgashi]

LGTM! To be honest looks simple not sure if we should have the molecule. I'll let @carlbuchmann decide on this.

[quulah]

I was going through all of my PRs and added the ssm_range to the test.

Rebased to current devel as well.

[carlbuchmann]

LGTM! To be honest looks simple not sure if we should have the molecule. I'll let @carlbuchmann decide on this.

@onurgashi - Yes, all PRs targeting eos_cli_config_gen requires a test - this allows us to refactor as required in time and insures the same outcome is preserved, it also eases the review process!

[titom73]

LGTM!

• Template: OK
• Documentation: OK
• Molecule: OK
• CI result: OK