[drift] Consider alternative configuration besides driftignore file

### TL;DR

The `driftignore` file is ok for describing a uniform list of assets to ignore but not good at describing complex rules such as

* Skip this project
* Skip this folder and all dependencies
* Skip this folder but not dependencies of it

We should consider moving to a yaml/json `driftconfig` configuration to allow for more complex configuration

NOTE: possibly still consider allowing a `driftignore` for the uniform list of assets? This would mean having both a `driftignore` and `driftconfig`.

### Detailed design

_No response_

### Alternatives considered

_No response_

### Additional information

_No response_

Look for existing driftignore parsing and usage in the codebase, likely in a config or ignore package. Understand how the tool currently processes ignore rules. Design a YAML/JSON configuration schema that can express complex rules like skipping projects or folders with/without dependencies. Consider how to maintain backward compatibility with driftignore.

Escrito por el modelo de indexación a partir del texto del issue.