text: Title: Wagtail choosers ignore Django's ForeignKey.limit_choices_to
  Body: ### Issue Summary
  If you set up a callable for a `ForeignKey.limit_choices_to`, It will get called by Django during form construction, but Wagtail's chooser system will never call that function, and thus not limit the choices presented in the chooser. This presumably also affects the other forms of `limit_choices_to` (see [here](https://docs.djangoproject.com/en/5.1/ref/models/fields/#django.db.models.ForeignKey.limit_choices_to)), but a callable is the easiest one to use as a robust example.
  
  ### Steps to Reproduce
  
  1. Build a basic bakerydemo, then apply the changes from here: https://github.com/wagtail/bakerydemo/compare/main...coredumperror:bakerydemo:limit_choices_to
  2. Open a BreadPage editor (which will cause `"limit_choices_to_bread"` to be printed to the console).
  3. Choose a BreadType (which will _not_ cause that print statement to fire).
  4. Every bread type is displayed in the chooser, instead of just ones with "bread" in their title.
  
  ### Technical details
  
  Python version: 3.12
  Django version: 5.1
  Wagtail version: 6.4.0
  
  ### Working on this
  
  Shouldn't this Django feature be supported by Wagtail's chooser system? It's quite surprising that my project's existing code, which worked fine when I wrote it years ago, has now stopped limiting the available options because Wagtail's new(ish) chooser system apparently just ignores it. 