Rename to Federated Calendar

Ship as Federated Calendar, with the application ID
computer.federated.FederatedCalendar and the executable
federated-calendar, so it can be installed and run alongside GNOME
Calendar.

The settings schema follows the application ID too, so the two don't
share settings or install the same schema. The project name sets the
executable, gettext domain and data directory; the desktop file, D-Bus
service, search provider, metainfo and icons follow the application ID.

Internal resource paths and the template file names are unchanged, to
keep merging from GNOME Calendar simple.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

meson.build

@@ -1,5 +1,5 @@
 project(
-  'gnome-calendar',
+  'federated-calendar',
                'c',
            version: '52.alpha',
            license: 'GPL3+',
@@ -45,11 +45,16 @@ else
   rev = ''
 endif
 
+base_application_id = 'computer.federated.FederatedCalendar'
 if profile == ''
-  application_id = 'org.gnome.Calendar'
+  application_id = base_application_id
 else
-  application_id = 'org.gnome.Calendar.@0@'.format(profile)
+  application_id = '@0@.@1@'.format(base_application_id, profile)
 endif
+
+# Settings are shared between profiles, but not with GNOME Calendar
+settings_schema_id = base_application_id
+settings_schema_path = '/' + settings_schema_id.replace('.', '/') + '/'
 calendar_buildtype = get_option('buildtype')
 development_release = calendar_minor_version.startswith('alpha') or \
                       calendar_minor_version.startswith('beta') or \
@@ -85,7 +90,8 @@ set_defines = [
   ['GETTEXT_PACKAGE', meson.project_name()],
   ['PROFILE', profile],
   ['NAME_SUFFIX', name_suffix],
-  ['APPLICATION_ID', application_id]
+  ['APPLICATION_ID', application_id],
+  ['SETTINGS_SCHEMA_ID', settings_schema_id],
 ]
 
 foreach define: set_defines