ECalBackendKolab: assign each cal backend its own KolabMailAccess instance
ECalBackendKolab: assign each cal backend its own KolabMailAccess instance

* each backend has its own cache directory,
  so we need to write KolabMailAccess cache
  data into these (i.e., configure KolabMailAccess
  accordingly)
* once each backend instance is given its own
  E-D-S process, we cannot share KolabMailAccess
  instances among backend instances any longer
  anyway

GNOME/evolution-kolab,GNOME/evolution-kolab