Changes in cache configuration does not invalidate artifacts

### Affected version

1.2.0

### Bug description

Hi,
I currently try to create a configuration for the maven build cache extension. Within that process I had some broken artifacts. Then I changed fixed configuration, but the extension did always restore the broken artifacts, because I he config is not included into the hash. This seems to be wrong for me.

I did found some workaround, with copying my configuration in a non hidden directory and specify that’s as part of my inputs, but it’s rather complicated. I would expect, that at least parts of the config will affect the hash calculation of the artifacts. Or that this usecase/limitation is documented.

P.S. I also thought, it is not explicitly stated in the documentation, that hidden files can’t be included as part of the inputs.

No source file, test, or entry point is named. Start by reproducing the cache behavior with a Maven build cache configuration change and trace how artifact inputs are hashed. Done means either relevant configuration changes invalidate cached artifacts or the limitation, including hidden-file handling, is documented.

Written by the indexing model from the issue text.