Support updating lifecycle scripts on existing containers

Because the container configuration is cached in the container labels after creation, any changes to the local config file are ignored for future operations on the container.

In the case of the lifecycle scripts (`onCreateCommand`, `postCreateCommand`, ...) it would be useful in cases of pooling container if changes to the config would be honored so that the container doesn't need to be recreated.

For example, if a container is created with an empty configuration for a pool, then we should be able to later change the configuration to and re-apply the post-creation lifecycle logic against the existing container.

```json
{
"postCreateCommand": "touch foo"
}
```

It would also be useful if the cli could detect the case of a configuration collision and fail with a reasonable message. For example, if the container is created with a `postCreateCommand` already and then the value is changed, then this re-application logic should fail.

首先跟踪 CLI 如何读取缓存的容器标签，并在对现有容器执行操作期间应用生命周期脚本。验证向现有容器添加脚本以及更改现有脚本时的行为；兼容的更改能够在不重新创建容器的情况下重新应用，并且冲突会以清晰的消息失败，即表示完成。

由索引模型根据 Issue 内容生成。