P: Filtered view - collapsing stack causes collapsed photos to inadvertently be added to target set

Collapsing a stack in a keyword filtered view where only the top photo in the stack has that keyword causes all of the collapsed photos to be added to the set of target photos.

Steps to reproduce:

- In grid view, apply a filter by keyword that contains stacked photos, where only the first photo in the stack has the keyword applied

- Select such a stacked photo

- If already expanded, collapse the stack.  If already collapsed, expand and then collapse.  It is the collapse action that triggers what I think is a bug.

Expectedly, the grid and filmstrip views do not change while in the filtered view except that the stacking badge for the selected photo changes between (n) and (1 of n).  Visually, this seems like correct behavior because the collapsed photos don't have the keyword.  However -

Unexpectedly, the action of collapsing the stack causes the collapsed photos to be added to the filtered set behind-the-scenes.  This is evidenced both in the result returned by the SDK function catalog:getTargetPhotos() as well as in the keyword list pane, where the check mark next to the filtered keyword changes from a check mark to a dash.  The filmstrip and grid views do not change, but the collapsed photos are added to the target set.  This could cause unintended actions to be done to the collapsed photos in addition to the one selected.

Environment: Win11, LrC 15.1, SDK 14.3.