Fix coverage data saving/rendering from embed plan

[thecalcc]

SDCP-863
SDCP-875

Front-end checklist

• This pull request is adding missing TypeScript types to modified code segments where it's easy to do so with confidence
• This pull request is using TypeScript interfaces instead of prop-types and updates usages where it's quick to do so
• This pull request is using memo or PureComponent to define new React components (and updates existing usages in modified code segments)
• This pull request is replacing lodash.get with optional chaining and nullish coalescing for modified code segments
• This pull request is not importing anything from client-core directly (use superdeskApi)
• This pull request is importing UI components from superdesk-ui-framework and superdeskApi when possible instead of using ones defined in this repository.
• This pull request is not using planningApi where it is possible to use superdeskApi
• This pull request is not adding redux based modals
• In this pull request, properties of redux state are not being passed as props to components; instead, we connect it to the component that needs them. Except components where using a react key is required - do not connect those due to performance reasons.
• This pull request is not adding redux actions that do not modify state (e.g. only calling angular services; those should be moved to planningApi)

[thecalcc]

@MarkLark86 this is the fix I found to be working so we persist the changes, and send the proper data back in the UI.

This is a follow up PR based on these comments - https://sourcefabric.slack.com/archives/C06HDLLA1SP/p1733139297225319

Let me know if that's how things should work, from my side there's no issues I see in the UI, and the changes do work.

[thecalcc]

All other changes are just improvements, this is the actual change that's fixing the issues mentioned in the linked tickets

[MarkLark86]

Hey @thecalcc
associated_plannings is set to undefined because we don't want to store this on the Event item itself (this happens for both create and update actions).

Instead what I would try is to re-populate this field after the response from the server/update action:

superdesk-planning/client/api/events.ts

Lines 199 to 202 in f690905

	.then((response) => {
	const events = modifySaveResponseForClient(response);
	return planningApi.planning.searchGetAll({

.then((response) => { 
    const events = modifySaveResponseForClient(response);
    
    events[0].associated_plannings = updates.associated_plannings
    return planningApi.planning.searchGetAll({ 

Can you please try that and see if that fixes the issue

[thecalcc]

Ok makes sense, just tried that and it does work

[MarkLark86]

Looks fine