[vue] Fix OneToOne fields binding in update entity select

[swarajsaaj]

Fix #15130

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (bellow reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[mshima]

At angular, ${relationshipFieldNamePlural}Collection Is filtered for one-to-one available values while ${otherEntityName}Collection isn't.
Don’t know about vue.

[swarajsaaj]

@mshima In Angular, somehow there are multiple ${relationshipFieldNamePlural}Collection arrays created (startLocationsCollection and destionationLocationsCollection) even for the same relationship target entity (HikingLocation).

generator-jhipster/generators/entity-client/templates/angular/src/main/webapp/app/entities/update/entity-management-update.component.ts.ejs

Lines 91 to 93 in 717d172

	<%_ for (const relationship of relationshipsWithCustomUniqueOptions) { _%>
	<%= relationship.relationshipFieldNamePlural %>Collection: I<%= relationship.otherEntityAngularName %>[] = [];
	<%_ } _%>

But in Vue, only a single array for options is created in component i.e. relationshipFieldNamePlural (hikingLocations)

generator-jhipster/generators/entity-client/templates/vue/src/main/webapp/app/entities/entity-update.component.ts.ejs

Line 306 in 717d172

this.<%= otherEntityNamePlural %> = res.data;

[mshima]

LGTM.

[swarajsaaj]

bounty claimed at https://opencollective.com/generator-jhipster/expenses/43269

[pascalgrimaud]

@swarajsaaj : approved and thanks for your work!