Fix Save button stop working issue

[usingtechnology]

Description

Fix the intended logic when adding a component with the API Key of form. Errors in that logic prevented the notification from displaying and prompting the form designer to remove that component.

See FORMS-982.
The issue reported was save button stops working.

CHEFs did (intend to) have a prompt to notify the designer that they cannot save a component with API key = form. That's where the button gets disabled. Without the prompt the designer doesn't know how much work or how many components would be lost to reset the button by clicking Undo.

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

• I have read the CONTRIBUTING doc
• I have checked that unit tests pass locally with my changes
• I have run the npm script lint on the frontend and backend
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• I have approval from the product owner for the contribution in this pull request

Further comments

Steps to reproduce (on existing code - use the dev instance)

1. Using Chrome, so you can open the Developer Tools | Javascript console.
2. Go to our dev instance and login with your IDIR - CHEFS Dev
3. Create a new Form, the setup information doesn’t matter, I did Public, no API Key.
4. In design, click Save, make sure it works.
5. Add a Panel, just save the component, no need to rename it.
6. Save Form again, ensure button works.
7. Drag on a component, could be a panel, checkbox, text… doesn’t really matter. Set the API property name = form, save the component to close the dialog.
8. You should see an error stack in the Javascript console.
9. The Form Designer Save button should be grey and not respond to clicks.
10. Drag another component out, don’t bother renaming anything, save it to close the dialog
11. Save button still disabled.

On this PR, at step 7 you should see an error notification indicating you cannot have a component named form. The component is in the form, so remove it or click Undo. You should then see the save button enabled and carry on adding/editing as before.

[github-actions]

Coverage Report (Application)

Totals
Statements:	45.24% ( 2944 / 6507 )
Methods:	41.81% ( 378 / 904 )
Lines:	51.03% ( 1954 / 3829 )
Branches:	34.5% ( 612 / 1774 )

[github-actions]

Coverage Report (Frontend)

Totals
Statements:	74.45% ( 16934 / 22745 )
Methods:	34.35% ( 270 / 786 )
Lines:	75.64% ( 16159 / 21363 )
Branches:	84.73% ( 505 / 596 )

[WalterMoar]

Looks great!