Certificate Expiry Hadling After 10 Years

Summary

Certificate Expiry Hadling After 10 Years

--- Basically did the same thing as in the qt platform ---

Auto reconfiguration of own certificate:

currently:
if kdeconncect loads its certificate and its expired or not effective yet
it generates a new certificate and deletes all remembered devices
( since these will stay unreachable anyways)

previously:
if kdeconncect loads its certificate and its expired or not effective yet
it continues having the same certificate
This brings forth an issue: Other devices would refuse to connect to a device with
an expired or non-effective certificate.

Auto-delete of orphan certificates:

currently:
Devices in kdeconnect's devicelist that have illegal ssl certificates
(expired, not effective yet, empty) get automatically deleted from the
devicelist
previously:
they would just exist forever until the user deletes them

Test Plan

Modified the date field in the certificates and threw the modified certificates into the /data/data/ directory of kde connect.

This was done for trusted devices as well as for the local certificate.