typo in whatsthis
before going further, remove the existing email annotation feature

this preserve the API for annotations, which will quietly change
in implementation to edit / fetch / etc notes for the email. this
will preserve code elsewhere such as for theming.
create the actual relation
we don't really care about errors in the end

relations can only be formed if the mail and the note are in the same
collection. so it is completely plausible for a relation to fail but
the note is created and stored in akonadi where requestsed.
don't defeat the optimization by creating new strings
update the implementation of the API to reflect that we are using realy notes
we no longer care about annotations, but relations
show the correct text for note create / edit based on note status
small steps towards the messagelist parts of notes working
if the note exists, update it rather than create a new one
if there is a note, then fetch the note info for editting before showing the note edit
don't show the note in the tooltip

loading it requires roundtrips (async, less performance) and the
note may be arbitrarily large?
these are not fixmes at this point
no longer consider this a FIXME either: the caller needs to load it
Collapse Person node always by default

KOLAB: 3623
Accountwizard: Add Editmode for different setupobjects

* for configfile (freebusy)
* for transport (smtp)
* for imap
* for ldap

KOLAB: 3728
Accountwizard: Added ldap setBaseDN

do not fail if no username is set (and test for edit mode).
Accountwizard: Moved setupInfo to public to make script be able to display messages
Accountwizard: Disable back button in last step.
Accountwizard: Added destroy option for ldap object.

ldapclientsearchconfig:
* Do not show the question for storing passwords in KWallet for LDAP
  (need for tests)

* Added test for ldap.destroy function