Add capabilities support for evo2-sync

[dgollub]

Capabilities support for evo2-sync actually should only consists of determining the version of evolution and reporting it via the OpenSync? version interface:

        const char *evo2_version = magic_evo_determine_version_function();
        OSyncVersion *version = osync_version_new(error);
        osync_version_set_plugin(version, "evo2-sync");
        osync_version_set_softwareversion(version, evo2_version);

And write capabilities and description files for evo2-sync which fits the evolution capabilities.

[tuju]

non-core plugins wont block releases. thus milestone == NULL.

[ianmartin]

The evolution plugin is really a connector to the evolution-data-server not just Evolutions local data store.

So the capabilities are different if you are using google calender or OWA or the local data store.

Therefore until you have connected to the data store it is impossible to tell what the capabilities of the resource are. So capabilities must be generated dynamically much like syncml will have to.

[felixmoeller]

Work has been done on this with r4413. I do not know whether is is finished.