Episerver - update 360

Steps to reproduce:

• Create a form that contains a Rich text element.
• Cut that element under For This Form folder and paste it into another folder.
• View the page that contains the form.

Expected result:
The page shows the form without any problems.

Actual result:
A NullReferenceException has been thrown.

Steps to reproduce:

1. Create a form with 2 elements and make the second element show if the condition is met on the first element.
2. Export the page with the form to a file.
3. Change the name of the first element in the form.
4. Import the form without updating existing content.
5. Go to the dependencies tab in the second element of the imported form.
6. The dependency has a crisscrossed background and the name of the dependent form element is the name of the changed element from the first form. 

Expected result:

Form field dependencies should work.

Actual result:

Dependencies for form elements do not get imported correctly and do not work. In the Dependencies tab in the imported form, the second text element's dependency points to the first text element in the original form.

Steps to reproduce:

1. Create a page in SV language that contains a form container.
2. Submit form.

Expected:

The text "The form has been submitted successfully." is translated correctly.

Actual:

The text "The form has been submitted successfully." isn't translated correctly in Swedish. It still displays: "Formuläret skickat.", which is the old translation and not the latest.

CleanupPartialSubmissions() incorrectly collects and removes both partial AND finalized submissions.

Submitted form events have been updated to support doing asynchronous calls before submitting data.

The ExpiredFormSubmissionRemoveJob loads all existing forms before performing a delete action on expired forms. This may cause performance issues if there are a lot of submitted forms.

The default controller can be overridden by editing the default coreController="/EPiServer.Forms/DataSubmit". This does not apply to the Hidden visitor profiling regarding the GetGeoData() method from the controller, since the URL used for calling that is hardcoded in the client resource javascript (EPiServerForms.js). A fix should be made here to get control of the GetGeoData and to be able to really customize the functionality.

Based on profiling data, StickySiteKpi can allocate a lot of objects and cause frequent GC gen 0.

A/B testing preview displays squashed text.