DesignView not re-rendering after converting a newly added layout to PDF (without currently implemented hack)

[standeren]

Description of the bug

In the component DesignView in ux-editor we are now referring to useFormLayoutSettingsQuery twice, where the first reference is unused, in order to force a re-render of the DesignView, which are listing the layouts in the current layout set.

This hack should actually not have any effect since the two references are listening to the same useState inside tanStackQuery, but for some reason it works.

This bug-issue involves removing the hack and figure out how we can ensure the correct behaviour of re-rendering DesignView after converting a newly added layout to a PDF without needing to force the re-render by a user-trigger. (e.g. clicking a page accordion in DesignView)

Video:
In the video you see how the behaviour is when the hack is present, and how the behaviour is when the hack is removed.

Skjermopptak.2024-10-02.kl.08.26.38.mov

Additional information

The issue arised in this PR

Steps To Reproduce

1. Remove the additional reference to useFormLayoutSettingsQuery in DesignView.tsx (currently located here)
2. Add a new page
3. Click the PDF accordion in the config-panel
4. Convert the current page to a PDF
5. See that the pages in the DesignView panel is not re-rendering even though the button text in the PDF accordion for the particular page has been updated (you can also check the cache or local changes to confirm that Settings.json has been updated)
6. Click on another page in the DesignView panel and see that the component re-renders

Additional Information

No response