Change replace pin behaviour to keep old content ids

[anjor]

Today the replacePin endpoint removes the old content, and adds the new content. This results in a situation where we have "gaps" in the content ids which can be a bit confusing.

Should we instead keep the old content as well but mark it as "replaced" with a flag in the database?