Thanks for the clarification @MathisGD. As you correctly point out, if the current Solidity codebase of Aave would be compiled and deployed again, the post-upgrade EIPs (optimizations, validations) would apply to the new contracts, most probably slightly changing the to-be-deployed bytecode.
We didn’t put much focus on that as the most critical aspect is production instances, but being precise, you are right.