[SrvBroker] Init/Deinit data to avoid resilient stored data

[CastagnaIT]

Description

Since it does not know when the system cleans the data in memory, the data stored by the singleton will remain persistent each time the add-on is used despite its instance is terminated by kodi core, so force clean components pointers

Motivation and context

another attempt to fix #1770

How has this been tested?

1. play any widevine stream
2. play any unencrypted stream
3. debug srvbroker vars and check the drm configuration, that must be empty

Screenshots (if appropriate):

Types of change

• Bug fix (non-breaking change which fixes an issue)
• Clean up (non-breaking change which removes non-working, unmaintained functionality)
• Improvement (non-breaking change which improves existing functionality)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that will cause existing functionality to change)
• Cosmetic change (non-breaking change that doesn't touch code)
• None of the above (please explain below)

Checklist:

• I have read the Contributing document
• My code follows the Code Guidelines of this project
• My change requires a change to the Wiki documentation
• I have updated the documentation accordingly

[CastagnaIT]

@lrusak last time you give me some hints
do you have time to take a look? should i make the data not persistently stay in memory in the singleton
could be good this solution? or are there more elegant solutions?