Modify ResourceSelector to use existing resource instance

[sharadsw]

Fixes #4865

When adding a form table subview, 2 resources were being created.

First one in FormTable.tsx: https://github.com/specify/specify7/blob/907d1524cfbc56380fc038b0f7a3663e7ff46576/specifyweb/frontend/js_src/lib/components/FormCells/FormTable.tsx#L458-L459

Which gets set as an expanded record and gets passed up the parent chain: https://github.com/specify/specify7/blob/907d1524cfbc56380fc038b0f7a3663e7ff46576/specifyweb/frontend/js_src/lib/components/FormCells/FormTable.tsx#L125-L132

But that resource instance gets lost in RecordSelector.tsx, which creates a new resource that does not get added to expandedRecords and gets passed all the way up to SubView.tsx https://github.com/specify/specify7/blob/907d1524cfbc56380fc038b0f7a3663e7ff46576/specifyweb/frontend/js_src/lib/components/FormSliders/RecordSelector.tsx#L128-L134

My change ensures RecordSelector uses the resource initialized by a child component.

Checklist

• [x] Self-review the PR after opening it to make sure the changes look good and self-explanatory (or properly documented)
• [ ] Add automated tests
• [x] Add relevant issue to release milestone

Testing instructions

For to-one relations:

• Use a Paleo database
• Go to Data Entry -> Collection Object
• Add a PaleoContext
  • [ ] Verify the PaleoContext subview is not collapsed by default
  • [ ] Verify data can be saved in the subview and persists on refresh
• [ ] Additionally, verify other subviews in the form still work like they used to

For interactions:

• Click on Interactions -> Gift
• Add a gift preparation
• Click on add unassociated item
  • [ ] Verify subview is not collapsed by default
• Add another gift preparation by using a record set with no preparations
  • [ ] Verify subview is not collapsed by default