Content Fragment Editor - Links with Personalization token gets removed due to Antisamy protection rules

Steps to reproduce
1. Create a new Content Fragment
2. Use Link Plugin to author a hyperlink containing personalization token. For example: <%= targetData.viewInBrowserLink %>
3. Save CF.
4. The Content Fragment gets saved as expected. We can also see the crx/de that the markup for CF shows the tag with personalization token in href.
5. Re-edit the fragment.
6. Notice that the link is completely removed by CF Editor.

We checked the logs and we see messages indicating that the links were removed due to XSS/Antisamy protection.

Start by reproducing the Content Fragment Editor steps and reviewing the XSS/Antisamy log messages described in the issue. Trace how the Link Plugin content is processed when the fragment is re-edited; done means a hyperlink containing the personalization token remains present after saving and reopening the fragment.

Written by the indexing model from the issue text.