fix(core): negated gitignore patterns inside subdirectories are not including matched files

[ekisu]

Issue # (if applicable)

Closes #9146

Reason for this change

When bundling assets with IgnoreMode.GIT, files that should be included via negation patterns (like !*.html) are incorrectly excluded if they're inside directories that are also re-included by negation patterns. Here's an example - consider the following tree:

- index.html
- app/
    - component.js
    - index.html
    - home.html

If we use a exclude pattern of ['*', '!*.html', '!*/'], the index.html in the root and both HTML files from the app folder should be included - the app folder shouldn't be excluded, due to the !*/ pattern. Right now, only the index.html file in the root folder is included.

Description of changes

Similar to #22002, I've updated the completelyIgnores logic that's used to check if we need to skip a directory tree to include a trailing slash before verifying whether it's an ignored pattern. This makes it properly match directory-specific negation patterns like !*/ by ensuring we're checking directory paths (with trailing slashes) against directory patterns.

I've also updated the logic in fingerprint to check if we're ignoring directories or files, and call completelyIgnores or ignores accordingly.

Describe any new or updated permissions being added

None.

Description of how you validated changes

Added unit tests covering the described scenarios.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

(This review is outdated)

[ekisu]

@aws-cdk-automation Clarification Request

How would I go about writing an integration test for functionality in the core package?

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.