Release notes for Optimizely CMS and Commerce updates

Steps to reproduce:

1. Create a project.
2. Navigate to the Export UI in CMS admin view.
3. Select the root page. Select "sub items" and "export files that the pages link to."
4. Click Export.
5. Delete any page. 
6. Check the # of rows in tblNotificationSubscription

   select count(*) from tblNotificationSubscription
   

1. Navigate to import screen.
2. Select the file from the previous import. Use the "update existing items with matching ID" option.
3. Begin import.
4. Check the # of rows in tblNotificationSubscription.

Expected result:
No increase in rows.

Actual result:
Rows increase.

Fixed an issue where the link validation job failed for relative links when no wildcard host was defined.

Fixed an issue that threw an SQL exception in SPROC netApprovalAdd when you requested an approval on a content item with an anonymous user. The SPROC expected that the parameter @StartedBy is not null.

HttpContext.User.Identity.Name has changed from "" (empty string) to null between .NET Framework and ASP.NET Core.

Fixed an issue where you could not have the same segment for a "simple address segment" in a multisite scenario. An error stated that the same address segment was already being used.

Fixed an issue where a trailing slash was added to external URLs, even though they were specified without one.

Fixed an issue where you could not add a local block inside a XHtmlString property of a local block in Quick Edit.

Fixed an issue where Publish Changes, Cancel and Save buttons were unreachable when you created a block through the TinyMCE Add local block.

Fixed an issue where an Internal Server Error (500) occurred when you requested project items in Project Overview from projects with large amount of items.

Fixed an issue where blocks place in the For this site folder were not included in the selection dialog box when you added blocks to a content area using Select Content in a site that uses site specific assets.

Fix an issue in Image Editor where large images were not handled properly for the image size vs crop size or zoom.