v1.3.6

build: ship a shlibs control file in the runtime package

The runtime package registered no dependency information for the
libfronius SONAME, so dpkg-shlibdeps in a downstream package aborted
with "no dependency information found for libfronius.so.1" instead of
emitting a Depends. Consumers had to either declare the dependency by
hand or leave it out entirely, in which case the resulting package
installed cleanly and then failed at exec with an unresolved SONAME.

CPACK_DEBIAN_PACKAGE_GENERATE_SHLIBS has no per-component variant, but
CPack resolves the package name per component before writing the file,
so only the runtime package gains an entry -- the devel package carries
just the dangling namelink, which is not an ELF object and is skipped.

The default policy is an exact-version match, which would pin every
consumer to the libfronius release it was built against and break the
install on any upgrade. The SOVERSION already guards the ABI, so >= is
the correct constraint.

Generated entry: libfronius 1 libfronius1 (>= 1.3.5)