Have one-to-one mappings between presentations and decks

[nmattia]

The current implementation of deck deploy (e.g. presentation) creates one presentation per deck name. This is wrong as the deck name may change. Instead a deck should have at most one presentation; when re-publishing a deck the backend should lookup the presentation and re-use it if it already exists.