Organize our rust code into `crates/` directory

ShaharNaveh

All of our current crates are scattered in the top level of the repository, it's not very intuitive for newcomers to look at the code and know that common directory is for shared rust code, and that wtf8 is also a crate for example.

I propose that we create a new directory called crates where we will have the following:

common -> crates/common Move common -> crates/common #6256
compiler/core -> crates/compiler-core Move compiler-core -> crates/compiler-core #6258
compiler/codegen -> crates/codegen Move compiler/codegen -> crates/codegen #6260
compiler/literal -> crates/literal Move compiler/literal -> crates/literal #6259
compiler/source -> crates/compiler-source Move compiler/source -> crates/compiler-source #6261
compiler/src -> crates/compiler Move compiler/src -> crates/compiler #6270
derive -> crates/derive Move derive -> crates/derive #6264
derive-impl -> crates/derive-impl move derive-impl -> crates/derive-impl #6263
jit -> crates/jit Move jit -> crates/jit #6262
pylib -> crates/pylib Move pylib -> crates/pylib #6225
stdlib -> crates/stdlib Move stdlib -> crates/stdlib #6268
vm/sre_engine -> crates/sre_engine Move vm/sre_engine -> crates/sre_engine #6265
vm -> crates/vm Move vm -> crates/vm #6269
wasm/lib -> crates/wasm Move wasm/lib -> crates/wasm #6280
wtf8 -> crates/wtf8 Move wtf8 -> crates/wtf8 #6257
src -> crates/rustpyton

I think it be better if we do those changes with many smaller PRs as not all of them would require changes to the CI, or any other changes. while minimizing the merge conflicts frequencies while we are in this transition.

For project examples that uses this workspace structure you can see: