Form Class is loading queries (too?) eagerly causing (unnecessary) performance bottleneck

[bnomei]

Describe the bug
Form class loads data even if it may be never used. it dataset is very big this causes a hugh delay for on each request. This is a common scenario in both autoid and boost plugin and currently make adding pages beyond 20k index impossible within 30sec timeout.

kirby/src/Cms/PageActions.php

Line 459 in efe24a6

$form = Form::for($page, [

To Reproduce

1. create a lot of pages of template human

2. create a collection that does return a site->index()

<?php

return function () {
    return site()->index()->filterBy('template', 'human');
};

3. create a page blueprint with a field with a multiselect query

# other fields
human:
  type: multiselect
  options: query
  max: 1
  query:
    fetch: kirby.collection('humans') # this does a site index -> filter
    text: "{{ page.title }}"
    value: "{{ page.id }}"

4. create a single or a batch of new human page programmatically.
5. the query will be executed in php code even it is most likely only used in api/kql/panel.

Expected behavior
the query should only be executed in context of api/kql/panel or when called explicitly in php.

Kirby Version
3.5.7 and 3.6.0-beta.1

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[bnomei]

dear bot. this issue has not been resolved. please keep it open.

[lukasbestle]

I think we should revisit what you wrote in "expected behavior": If we can find a way to resolve the options less often and only when they are needed, this will increase performance by a lot, no matter if a cache is used or not.

[distantnative]

We have started refactoring our blueprint and form classes. Would be best to tackle this, once that's done.