Index selected sub fields in JSON column

Today, all the nested fields of a JSON column are indexed during the index creation. This leads to unnecessary storage cost, if users know beforehand what nested fields are needed in the predicates. However, users may want to keep the entire JSON column in the projection list. It'll be good to enhance the JSON index spec and allow users to specify the nested fields to index.