Description

Currently we only update assets when we detect either a change to an existing asset or an update to the asset manifest. Due to the existence of wildcard assets foo/ (all files directly under foo), it is possible for a user to add a new asset which isn't detected through either of these previous approaches.

To fix this, we can track each wildcard directory in addition to the asset manifest, and mark the bundle as needing to be updated when the directory stat has occurred after the last build time. This allows adding a new asset to a wildcard directory and hot reloading it.

Related Issues

Fixes #18896

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes tests for all changed/updated/fixed behaviors (See Test Coverage).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require Flutter developers to manually update their apps to accommodate your change?

• Yes, this is a breaking change (Please read Handling breaking changes).
• No, this is not a breaking change.