Change Details

By moving `primitives/transaction.cpp` from `bitcoinconsensus` to `common`, we can keep it and `primitives/blcok.cpp` together in one library. This will remove the need to include `bitcoinconsensus` as part of the seeder library when the chainparams facilities are introduced. Discussed previously with Fabien.

There is a circular dependency that is currently hidden in CMake builds. chainparams.cpp from `common` requires `primities/transactions.cpp` from `bitcoinconsensus` which also depends on `common`. This is hidden in every other build by linking `common` before linking `bitcoinconsensus`. By moving `primitives/transaction.cpp` from `bitcoinconsensus` to `common`, we can keep it and `primitives/block.cpp` together in one library. This will remove the circular dependency mentioned above. Discussed previously with Fabien.

By moving `primitives/transaction.cpp` from `bitcoinconsensus` toThere is a circular dependency that is currently hidden in CMake builds. chainparams.cpp from `common` requires `primities/transactions.cpp` `common`, we can keep it and `primitives/blcok.cpp` together in onefrom `bitcoinconsensus` which also depends on `common`. This is library. This will remove the need to include `bitcoinconsensus` ashidden in every other build by linking `common` before linking `bitcoinconsensus`. By moving `primitives/transaction.cpp` from `bitcoinconsensus` to part of the seeder library when the chainparams facilities are`common`, we can keep it and `primitives/block.cpp` together in one introducedlibrary. This will remove the circular dependency mentioned above. Discussed previously with Fabien.