A bug about version 0.13

**Describe the bug**
A clear and concise description of what the bug is.
I download the binary v0.13 from[https://github.com/SteveYurongSu/apache-iotdb-nightly-releases]( https://github.com/SteveYurongSu/apache-iotdb-nightly-releases).
It generates the following bug:


**To Reproduce**
Steps to reproduce the behavior:
1. create storage group root.CNNP.QF."01";
2. CREATE aligned TIMESERIES root.CNNP.QF."01"(QF_01_1RCP108MV_AVALUE FLOAT ENCODING=GORILLA compression=SNAPPY);
3. select QF_01_1RCP108MV_AVALUE from root.CNNP.QF."01";

**Expected behavior**
A clear and concise description of what you expected to happen.

> Msg: 322: Storage group is not set for current seriesPath: [root.CNNP.QF]

**Screenshots**
If applicable, add screenshots to help explain your problem.


**Desktop (please complete the following information):**
- OS: [windows10]
- IoTDB 0.13, java 11

**Additional context**
Add any other context about the problem here.

Reproduce the issue with IoTDB 0.13 on Java 11 using the three SQL statements in the report, then inspect the storage-group and aligned-timeseries handling involved in the reported series path. Done means identifying why the query reports that no storage group is set and adding a regression test or documenting the confirmed expected behavior.

Written by the indexing model from the issue text.