improve plugin-name example config file

[mkoller]

it would be helpful if the file "plugin-name" ./opensync/docs/example-plugin/src/plugin-name would actually contain an example of some config options instead of the text it currently holds, e.g. matching the implementation of plugin.c where I see how to use the advancedoptions

[dgollub]

This is still present for current trunk.

[Bloosky]

Something to start with. Anyone can check/improve it?

<!-- This file will hold the default configuration options of your plugin. -->

<?xml version="1.0"?>
<config version="1.0">
  <!-- Advanced options (optional)-->
  <AdvancedOptions>
   <AdvancedOption>
     <!-- Advanced option settings -->
     <DisplayName>advanced_option</DisplayName>
     <Name>option_name</Name>
     <Type>option_type</Type>
     <Value>option_value</Value>
   </AdvancedOption>
  </AdvancedOptions>

  <Resources>
    <Resource>
     <Enabled>1</Enabled>
     <Formats>
       <Format>
         <!-- Format name (vevent20, vtodo20, vcard30, ...)-->
         <Name>format_name</Name>
       </Format>
     </Formats>
     <!-- Object type (event, todo, contact, ...) -->
     <ObjType>object_type</ObjType>
     <!-- Path to sync -->
     <Path>/path/to/sync/</Path>
    </Resource>
  </Resources>
</config>

[dgollub]

(In [5999]) Added some simple plugin configuration with resources configuration. Even that resources configuration is optional. Most plugin starts might want to start with hardcoded resources configuration.

fixes #922