assets: hashing does not have any (debug) output

### Describe the feature

Calculating the hash can be very time consuming if the source for the hash is very large. Typically this can happen when `node_modules` is included in the source.

Currently there is no debug information available when hashing is happening. This is very confusing when hashing takes a long time.

### Use Case

As a user,
When CDK creates the asset hash for a very large source directory,
I want to see that hashing happens and how long it takes,
So that I can optimize my CDK app.

### Proposed Solution

With one level of verbosity:
- Add some debug output for every call to `calculateHash` at the start showing the asset name and hash type.
- After hashing the hash should be printed and the time it took

With two levels of verbosity:
- Print additional information on the hash configuration

### Other Information

_No response_

### Acknowledgements

- [X] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### CDK version used

2.61.1

### Environment details (OS name and version, etc.)

macos

Start by locating the calculateHash entry point in the CDK source and inspect how debug verbosity is handled around asset processing. Done means one verbosity level reports the asset name, hash type, resulting hash, and elapsed hashing time, while two levels also report the hash configuration.

Written by the indexing model from the issue text.