Issue Summary

During a s2c migration with JCMA, the field renderers and required option are not migrated as part of the field configuration settings.
Taking a multi-line text field as an example, it'd mean that post-migration, the field renderer will be set to its default value of Default Text Renderer and the field would be created as optional, but the render and required option are correctly exported.

But if the same custom field is later migrate and merged with the previous one existing on cloud, it will be corrected to the wiki render and required option.

Steps to Reproduce

1. Create a new multi-line text custom field
2. Associate the custom field with a project
3. Modify the field configuration and change the custom field's renderer to Wiki Style Renderer and required and associate it with a Screen
4. Migrate the project using the JCMA to a clean cloud instance
5. Observe the field configuration in the destination site
6. Delete the project, while leaving the screen and custom field in cloud
7. Remigrate the project without performing any change in server.
8. Observe the field configuration in the cloud again, and notice that now it show the correct render and required option.
   1. Callout - if the custom field is not associate with any screen it doesn't get corrected with the remigration.

Expected Results

The field configuration settings are migrated with the render and required option correctly set as per the source.

Actual Results

The field configuration settings are not migrated and the field renderer is set to Default Text Renderer and the required option is missing, only after remigrating it gets corrected.

Workaround

Manually modify the field configuration after migration and change the renderer to the correct renderer and update the required option.

• Specify field behavior - Change a field's renderer
  Or Remigrate the project with the custom field associated with screens.