Include groupemails_enabled attribute in file exports for offline transfer

Summary

In direct transfer, groups are imported in two steps

1. The base portable is created in BulkImports::Groups::Pipelines::GroupPipeline. This pipeline makes GraphQL queries to the source destination, which won't be possible in offline transfer.
2. Attributes for the newly created portable are updated in BulkImports::Groups::Pipelines::GroupAttributesPipeline from self relation files.

emails_disabled is fetched in GroupPipeline then negated and set to emails_enabled in its transformer. It's not currently present in the self relation file, so it must be included in that file in order to import the source created date in offline transfer.

Proposed implementation

Add emails_disabled to group/import_export.yml.

Effects on other importers

• File-based group import/export would now preserve the source group's email notifications setting. We probably want this, but it should be confirmed. We may need to communicate the change even though file-based group imports are deprecated
• Direct transfer would be unaffected since it's already imported