Vet Center services added through IEF bypass allow_only_one_validation

[swirtSJW]

Describe the defect When editing a vet_center it is possible to add/create duplicate services even though duplicate service creation is prevented by the allow_only_one field on the content type

Saving the service directly prevents the creation of duplicate

However creating using inline entity form does not.

It is uncertain at this time if this is a bug with IEF or with Allow Only One.

There are some validation issues on the IEF issues board that might be related

1. https://www.drupal.org/project/inline_entity_form/issues/2926859 (has a patch)
2. https://www.drupal.org/project/inline_entity_form/issues/2780079 (seems similar but no helpful information)
3. https://www.drupal.org/project/inline_entity_form/issues/2821343 (likely the result of #1, nothing helpful)

I have created this issue on allow_only_one for use IF this is a bug in that module
https://www.drupal.org/project/allow_only_one/issues/3225757 If it turns out to be an IEF issue that is resolved by the patch, then add a link and note to the allow_only_one issue.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information if relevant, or delete):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here. Reach out to the Product Managers to determine if it should be escalated as critical (prevents users from accomplishing their work with no known workaround and needs to be addressed within 2 business days).

Labels

(You can delete this section once it's complete)

• [x] Issue type (red) (defaults to "Defect")
• [ ] CMS subsystem (green)
• [ ] CMS practice area (blue)
• [x] CMS objective (orange) (not needed for bug tickets)
• [ ] CMS-supported product (black)

CMS Team

Please leave only the team that will do this work selected. If you're not sure, it's fine to leave both selected.

• [x] Core Application Team
• [x] Product Support Team

[kevwalsh]

Related, will solve this problem in a different way, and improve UX. But also further obscure this defect. https://github.com/department-of-veterans-affairs/va.gov-cms/issues/5888 (fixed in https://github.com/department-of-veterans-affairs/va.gov-cms/pull/5915 )

[davidmpickett]

This defect will be resolved once the IEF changes are implemented. Leaving this defect in backlog to confirm and close after https://github.com/department-of-veterans-affairs/va.gov-cms/issues/18003

[jilladams]

Can be validated / closed when #18003 ships

[davidmpickett]

Verified on Prod