chore: refactor to move endpage block to generic folder

[kathleenkhy]

Problem

Related to PR (#7232) to refactor by moving EndPageBlock.tsx file to a generic folder (out of the public-form folder) - this is to reduce confusion that the EndPageBlock.tsx is not entirely isolated to the public-form context and may cause downstream bugs and issues if the component is rendered incorrectly.

Pushing out a new PR since the previous PR is quite behind the develop branch after launching MRF, and local can't run properly even after resolving conflicts.

seems easier to re-do the chore on the new dev branch

Closes FRM-1710

Solution

By moving EndPageBlock.tsx to a generic folder that is not within public-form or admin-form

Tests

• Create a non-payment form
• Proceed to the Thank You page tab that it is working as intended
• Check Preview that the Thank you page is rendered properly
• Open the form and make a submission - check that the Thank You page is rendered properly
• Create a payment form
• Proceed to the Thank You page tab that it is working as intended
• Check Preview that the Thank you page is rendered properly
• Open the form and make a submission - check that the Thank You page is rendered properly

MRF Form test

• Create an MRF form
• Create 2 workflows
• Submit the 1st workflow - the Submit another response button should be present
• Submit the 2nd workflow - the Submit another response button should not be present

[linear]

FRM-1710 Move EndPageBlock from `public-form` folder to generic component folder

[KenLSM]

import { ThankYouSvgr } from '~features/public-form/components/FormEndPage/components/ThankYouSvgr'
import { PaymentsThankYouSvgr } from '~features/public-form/components/FormEndPage/components/PaymentsThankYouSvgr'

these two seem to also be likely candidates to move over to the generic folders together?

[kathleenkhy]

yup that makes sense! I'll add these 2 Svgr files to the generic components folder FormEndPage too

[KenLSM]

LGTM! Thanks @kathleenkhy