* test merging aspects

* fix: use custom merge functions for modules and resolve options (#23)

When merging aspect configs across scopes (e.g. bar = config.foo), the
modules and resolve options were incorrectly merging pre-computed values
from individual scopes instead of recomputing from the merged config.

The fix uses custom type merge functions that always recompute from the
final merged config, ensuring resolved modules reflect all merged aspect
definitions.

* dont merge modules and resolve

---------

Co-authored-by: Albert O'Shea <albertoshea2@gmail.com>

This reverts commit 1df56b461c4fb233b7547e0623d4b60a127598be.

This reverts commit 72ffc008e2df05daf041bbf6511d17aa94e869a3.

* split tests, reorg types

and also funcion-to-module if lib,config,options detected.
Related: https://github.com/vic/den/issues/92

See:
https://github.com/vic/den/discussions/91#discussioncomment-14978857

let the functor just return a constant function

provides.itself ignores its arguments

Clarified usage of aspects system without flakes in README.

* aspect-chain contains aspect objects nor their names.

this is useful because we also have anonymous aspects
being the result of providers. even when these anonymous
aspect can be given an explicit name via `name` attribute,
it is better to pass the object itself.

* Apply suggestion from @Copilot

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

This reverts commit 66140439b9044de62dd45884b30d3f2e99f1540c.

Added badges and updated image references in README.

asp was short of aspect, but asp reminded be of dark lord micorosft

This allows providers an opportunity to inspect
the chain of aspects that caused they to be
included and can return accordingly.

also alias config as `aspects` arg in `flake.aspects` module.

Clarify the explanation of aspect functions in README.

* test aspect providers

* fix test

fix argument of providers to be just aspect and name.