We need to ignore the published_data.json resource during creation and create it from the item data during deployed

[chris-fox]

This is a spin off of #1209. When you create and publish a story map, briefing or collection (all the same item type) there are 2 resources created, draft_xxxxxx.json and published_data.json. Currently when we create a solution from a story map we ignore the draft_xxxxxxx,json file and when we deploy we create a new one and use the item data property to generate the json for the draft resource. This ensures the draft matches the item data.

It appears recently the published_data.json was introduced and this file is also generated when you publish the story map. It also appears to be the file that is read when displaying the published version of the story map. Currently we are treating this file like any other resource and is copied with the item during deployment. This causes the published version of the story map on deployment to be pointing at old items (i.e not swizzled).

So this request is to do the following:

• On creation, ignore the published_data.json, don't include it as a resource of the template
• On deployment, copy the swizzled item data and store it as the published_data.json resource. This is the same as we are currently doing with the draft_xxxxxxx.json file

You can test this with the following group. It contains the 3 flavors of story maps and also a referenced web app and survey123 form

https://localdeployment.maps.arcgis.com/home/group.html?id=b89df835727a42e7947eceb49dfa3f6d#overview

[chris-fox]

Verified