Create ServiceInfo files configuration from annotated ConfigMaps

[empovit]

Allow a user to pre-populate the content of ServiceInfo files by creating ConfigMaps even before creating an instance of the FDOOnboardingServer (ServiceInfo API server). Annotating the ConfigMaps with the required pieces of information - that is the permission, destination path, and filename (in case of multiple files in a ConfigMap) - relieves the user from manually entering this configuration into the CR. Using ConfigMaps also makes it easier to verify that a file exists before mounting it into the server pod. The downside is the size limitation of a ConfigMap, but for now we'll assume that onboarding files are small, and all the heavy lifting is left to the management platform once a device has been onboarded.

[empovit]

/cc @fabiendupont @mresvanis

[mresvanis]

/lgtm