[sub-PR] Constrain useFirestoreConnect query types to enforce our firestore query patterns

[0xdevalias]

Sub-PR to #801 that constrains the useFirestoreConnect query types to enforce our firestore query patterns.

This reinstates and improves upon the original type narrowing intended by #784, as called out in #801 (comment)

[0xdevalias]

If you want to play around with this in your IDE to see the type correctness, these are the 'manual test cases' I was using:

const foo1: SparkleRFCollectionQuery = {
  collection: "users",
};

const foo1Invalid: SparkleRFCollectionQuery = {
  collection: "users",
  storeAs: "users", // not allowed to use the name of a root collection in storeAs
};

const foo2: SparkleRFCollectionWhereQuery = {
  collection: "users",
  where: ["some id", "in", ["a"]],
  storeAs: "chatUsers",
};

const foo2Invalid: SparkleRFCollectionWhereQuery = {
  collection: "users",
  doc: "aaa", // doc not allowed for this type
  where: ["some id", "in", ["a"]],
  storeAs: "chatUsers",
};

const foo3: SparkleRFSingleDocumentQuery = {
  collection: "users",
  doc: "foo",
  storeAs: "chatUsers",
};

const foo3Invalid1: SparkleRFSingleDocumentQuery = {
  collection: "users",
  doc: "foo",
  where: ["some id", "in", []], // where not allowed in this type
  storeAs: "chatUsers",
};

const foo3Invalid2: SparkleRFSingleDocumentQuery = {
  collection: "users",
  doc: "foo",
  subcollections: [], // subcollections not allowed in this type
  storeAs: "chatUsers",
};

const foo4: SparkleRFSubcollectionQuery = {
  collection: "users",
  doc: "foo",
  subcollections: [],
  storeAs: "chatUsers",
};

const foo4a: SparkleRFSubcollectionQuery = {
  collection: "users",
  doc: "foo",
  subcollections: [],
  where: ["some id", "in", []],
  storeAs: "chatUsers",
};

const foo4Invalid: SparkleRFSubcollectionQuery = {
  collection: "users",
  // missing required doc
  subcollections: [],
  storeAs: "chatUsers",
};

// Note: this is just here to remove any 'variable is not used' errors
console.log(
  foo1,
  foo1Invalid,
  foo2,
  foo2Invalid,
  foo3,
  foo3Invalid1,
  foo3Invalid2,
  foo4,
  foo4a
);

Depending on how your IDE surfaces type errors, you'll see something like the following when hovering over one of the invalid configs:

[0xdevalias]

[OOS] We should remove this code file if it's not being used anymore