PCBNew collision detector does not highlight overlapping footprints that are part of a group unless you enter the group

Description

When you move footprints you expect to see the footprints that overlap our selection to become highlighted to advise us not to place footprints so close. In practice, this works for the following kinds of selections (written as "current selection to overlapping footprints":

1. One (selection) to one (footprint)
2. One to many
3. One to group
4. One to many groups
5. Many to one
6. Many to many
7. Many to group
8. Many to many groups

Cases that are not covered:

7. One group to one
8. One group to many
9. One group to one group
10. One group to many groups
11. Many groups to one
12. Many groups to many
13. Many groups to one group
14. Many groups to many groups

If we make our selection a group, without entering inside it, the collision detector does not highlight the overlapping footprints.

The only way to make it highlight is to enter the group and to move all the footprints and graphics inside it as a selection, not a group. This of course does not work in case you have multiple groups selected.

Steps to reproduce

1. Make a grouping of footprints.
2. Place a single footprint outside the group.
3. Move the group as a whole so that it overlaps the footprint that is alone.
4. Upon overlapping the alone footrpint, this does not get highlighted.

KiCad Version

Application: KiCad PCB Editor x64 on x64

Version: 7.99.0-3969-gc5ac2337e4, release build

Libraries:
	wxWidgets 3.2.4
	FreeType 2.12.1
	HarfBuzz 8.2.1
	FontConfig 2.14.2

Platform: Windows 11 (build 22631), 64-bit edition, 64 bit, Little endian, wxMSW

	wxWidgets: 3.2.4 (wchar_t,wx containers)
	Boost: 1.83.0
	OCC: 7.7.1
	Curl: 8.4.0-DEV
	ngspice: 41
	Compiler: Visual C++ 1936 without C++ ABI

Build settings: