As a next step we will want to proceed with implementing content-mapping functionality that allows automatically
moving the content from the existing url over to new system. We will start by processing content pages and proceed to
other data types in next tasks.
This process can be executed only on content page type entries that have content template selected 

There are few key steps we will want to have for this implementation:
- decide if new page is to be added or select an existing one (with check if the page template matches specified, if it does not, ask whether to keep that one or switch)
- load html content from the origin url for processing.
- retrieve content structure from the specified template (lets focus on fixed-layout templates for now, flexible templates will be looked at later).
- we want to extract fixed elements like page meta title, description, index, meta image for seo_data structure mapping
- we will want to figure out how to map the layout from the structure for template. We will try to automate this by using the OpenAI API that is currently added in system for generating vehicle descriptions. We will need a different prompt created for this as current one is specifically for generating vehicle description
- we provide the offered mapping by showing how the data would be implemented and ask user to confirm whether data looks ok or not.
- If not approved a comment box needs to be filled out allowing to specify what is incorrect and should be adjusted before trying again.
- If approved this mapping is stored for this template to avoid repeating AI calls for mapping across the same template.
- Content then is mapped to the content page 
- Button is presented to preview page on site and confirm whether it was migrated ok or not. 
- If not approved, then need to allow retrying mapping/import once again specifying what went wrong
- If approved the content entry is marked as text & imagery migrated, but not as checked.

Important notes about content structure migration!
- Imagery cannot be imported as part of text block
- Imagery is not copied over as a url, but imported using media facade
- use existing functionality like MapsContent trait to determine structure. Content structure is often nested in multiple layers, so auto-guessing how many layers of depth needs to be considered will not work
- use pageRepository::isContentOutOfSync() check to ensure page content is assigned the correct structure.

We also need to allow specifying content category (e.g. blog/news) in entry list section. This then carries over to page when content process is done. 
