[Feature Request] Share Move libraries between Move blockchain projects

# 🚀 Feature Request

## Motivation

Now we have several Blockchain projects using Move, but it is hard to share Move libraries between different blockchains.

Perhaps the ideal way of Move project dependency like:

```

┌─────────────┐
│Move Std lib │
└─────────────┘

┌─────────────┐ ┌───────────────────┐
│Move DeFi lib│ │Move Commons lib │
└─────────────┘ └───────────────────┘

┌───────────────────────────────┐
│ Move Chain independent lib │
└───────────────────────────────┘

┌───────────────────┐ ┌───────────────────┐ ┌───────────────────┐ ┌───────────────────┐
│ StarcoinFramework │ │ DiemFramework │ │ 0lFramework │ │ PontemFramework │
└───────────────────┘ └───────────────────┘ └───────────────────┘ └───────────────────┘

```

1. Move std lib: provide the basic modules for Move language.
2. Move DeFi lib: provide the basic modules for DeFi, such as Token and NFT standards.
3. Move Commons lib: provide some utils module for Move language, like java's apache-commons.
4. Frameworks: the chain-specific modules.

However, this is not yet possible and there is an address conflict issue.

Move stdlib uses the `0x1` address and will conflict with the framework. For example, if StarcoinFramework defines a dependency on Move stdlib in `Move.toml`, the Move project will produce an error.

One approach to resolve this is to auto-embed Move stdlib and Move DeFi lib to the chain framework, but this also has the problem of naming conflicts.

I think this is very important for building the Move ecosystem, and this is an advantage of Move over Solidity ecosystem.

**Is your feature request related to a problem? Please describe.**

## Pitch

**Describe the solution you'd like**

**Describe alternatives you've considered**

**Are you willing to open a pull request?** (See [CONTRIBUTING](../../CONTRIBUTING.md))

## Additional context