Enhance Sync telemetry

[mahalakshme]

As an implementation engineer, I would like to monitor the sync failures and resolve them even before they are raised as tickets.
I would also like to analyse the sync timings.

Acceptance criteria:

Changes in server tables:

• Add a column is_first_time_sync to sync_telemetry table. Reference query for the same can be found here: https://github.com/avniproject/avni-server/blob/26e1fd8029d72a1edc3e0091971e266b378cb809/avni-server-api/src/main/resources/database/usefulQueries.sql#L790
• Create a table for sync_failure_telemetry with below columns:
  - sync_telemetry_uuid from sync_telemetry_table
  - error_message
  - stacktrace
  - close_date_time
  - is_closed
  - created_date_time
  - last_modified_date_time
  - created_by_id
  - last_modified_by_id

Changes in realm tables:

• Add 2 columns error_message and stack_trace to the realm sync_telemetry table. Other columns are not required since entries of sync_telemetry are only pushed to server and not pulled.

• When the sync_telemetry entry is pushed to the server, add the expected data in the respective table/columns in the server tables.

Out of scope:

Adding a UI like rule failure telemetry. We can do it, once the newly added columns starts getting used.

[mahalakshme]

• saving sync_telemetry - and impact on performance?
• not connected to internet - handle it and not log sync failure
• bugsnag correlation add in the table instead of stacktrace.

[mahalakshme]

duplicate: #1175