Feat/common modules and fork specific folders

[amkCha]

• OOB modules has a difference in the array's size of one of the columns between London and Shanghai. The files impacted are therefore : columns.lisp + constancies.lisp + create.lisp
  => for OOB, there are now 2 subfolders
  

• the HUB module is a much bigger module. The impact of Shanghai comes from the difference in the OOB module as well as the instruction-handling of PUSH0
  => for the HUB, the folder is not duplicated. I've added a subfolder called xxx-fork whenever 2 files needed to be duplicated. For instance, in intruction-handling for push_pop
  
  Or for miscellaneous file column
  

• In the Makefile, we now compile zkevm_london.bin and zkevm_shanghai.bin. To compile the Hub for one fork or the other, we just need to filter out _lon.lisp or _shan.lisp file depending on the case. For the London Hub for example

HUB_LON :=  $(filter-out %_shan.lisp, $(wildcard hub/*.lisp)) \
			$(filter-out %_shan.lisp, $(wildcard hub/**/*.lisp)) \
			$(filter-out %_shan.lisp, $(wildcard hub/**/**/*.lisp)) \
			$(filter-out %_shan.lisp, $(wildcard hub/**/**/**/*.lisp)) \
			$(filter-out %_shan.lisp, $(wildcard hub/**/**/**/**/*.lisp)) \
			$(filter-out %_shan.lisp, $(wildcard hub/**/**/**/**/**/*.lisp))

[DavePearce]

It looks good to me, and I only have minor comments. I personally would have thought a naming scheme such as e.g. txndata/london is preferable to txndata/txndata-lon. But, its not a big deal at all!!

Also (just another suggestion) you have e.g. this:

hub/constraints/create/push-pop-fork/push_pop_lon.lisp
hub/constraints/create/push-pop-fork/push_pop_shan.lisp

I would do this instead:

hub/constraints/create/london/push_pop.lisp
hub/constraints/create/shanghai/push_pop.lisp

I would actually probably go further even. I'd move all the stuff in create/constraints into just create and then you could have generalities_lon.lisp as create/london/generalities.lisp, etc.