Expand all alias applications (in order) before internalising a pattern

The current implementation (as of runtimeverification/hs-backend-booster#22 and runtimeverification/hs-backend-booster#29 ) expands aliases only in one expected place: the LHS of a rewrite rule.
(in runtimeverification/hs-backend-booster#29, we are ignoring priority aliases for the unused antiLeft to avoid a problem caused by applying one alias inside another).

Instead, all aliases should be expanded immediately while internalising patterns (i.e., inside other aliases and in rules, both LHS and RHS). The underlying assumptions are:

1. all aliases in the kore file are declared before they are applied (location-wise)
2. aliases are only applied inside the module where they are declared

Given assumption 2. the internalised definition could discard all aliases once the module has been internalised, they do not have to be stored (we can also keep them around, though).

Start by tracing the current alias expansion during pattern internalisation, especially the LHS-only behavior described alongside runtimeverification/hs-backend-booster#22 and #29. Done means aliases expand immediately and in declaration order inside aliases and both sides of rules, while respecting the stated module and declaration-order assumptions.