Inverted FK direction from Resource to StoredData to fix N+1 on resource search list.

[axl8713]

These changes address the issue reported here, where a N+1 problem emerged when listing Resources; all the StoredData associated with Resources were loaded even with includeData=false, causing a performance drop for long lists of resources.

[axl8713]

@offtherailz How to name the SQL migration scripts? Should they reflect an older version?

[tdipisa]

@axl8713 please let's wait 2.6.0 to be released before merging the backport of this one.

[axl8713]

@tdipisa Waiting confirmation about migration scripts version numbers before merging.

[tdipisa]

@tdipisa Waiting confirmation about migration scripts version numbers before merging.

@axl8713 the following is fine as it follows the same naming convention followed so far.

doc/sql/migration/xxx/xxx-migration-from-v.2.4.1-to-v2.6.1.sql

going to merge...

@axl8713 please create an issue to connect to this PR for tests.

[offtherailz]

Created backport PR for 2.6.x:

• [Backport 2.6.x] Inverted FK direction from Resource to StoredData to fix N+1 on resource search list. #580 with remaining conflicts!

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-577-to-2.6.x
git worktree add --checkout .worktree/backport-577-to-2.6.x backport-577-to-2.6.x
cd .worktree/backport-577-to-2.6.x
git reset --hard HEAD^
git cherry-pick -x 34f33a807e280dcbc75bca39ea955876b234dbc4
git push --force-with-lease