[Java] ComplexWriter should initialize nested writers when container vector is already populated

It's possible and sometimes useful to use reuse a nested vector that was populated in a previous ComplexWriter. The new ComplexWriter should be aware of the fields that are present in the vector.

As it is right now, if a particular column were determined to be a specific type (or a union type), but the new writer finds a new type, the original type may be thrown out. What should happen is that the type should be promoted to union (or have a new subtype added to the union field).

**Reporter**: [Steven Phillips](https://issues.apache.org/jira/browse/ARROW-326) / @StevenMPhillips

_{**Note**: *This issue was originally created as [ARROW-326](https://issues.apache.org/jira/browse/ARROW-326). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*}

首先定位 ComplexWriter 以及從現有容器向量初始化巢狀 writer 的程式碼。重現 issue 中描述的已填入向量情境，然後驗證現有型別會獲得保留，且新型別會將欄位提升為 union 或新增 subtype，同時不會遺失先前的型別。

由索引模型根據 Issue 內容生成。