The changes excluded from a release note still count against its limit and can trigger the truncation warning

The releasenotechanges macro takes an exclusions parameter listing the changes not to display, and a limit parameter bounding how many changes each section displays.

The excluded changes are taken out of a section only after its page of changes has been fetched, so they still count against the limit:

• a section displays fewer changes than the limit allows, although more changes that are not excluded exist;
• the truncation warning ("some changes are not displayed, raise the limit") appears although every change that is not excluded would fit.

Steps to reproduce

1. Create a release note holding 3 user changes with a screenshot, Entry001 to Entry003.
2. Put {{releasenotechanges limit="2" exclusions="<full name of the Entry001 page>"/}} in its content.

Expected: Entry002 and Entry003 are displayed, and there is no truncation warning.
Actual: only Entry002 is displayed, and the truncation warning is shown.