allow list fields as metadata in Marqo (#277)

[tomhamer]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  This change means that marqo is able to accept non-tensor list fields. This is useful so that users can do "contains" operations on list metadata. [ENHANCEMENT] Support list and dictionary data structures #277

• What is the current behavior? (You can also link to an open issue here)
  Currently, marqo does not allow users to add lists as metadata.

• What is the new behavior (if this is a feature change)?
  Marqo allows users to add metadata as non_tensor fields, meaning they are available for filtering and lexical search

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
  no

• Have unit tests been run against this PR? (Has there also been any additional testing?)
  pending succesful unit test run, handing this off for completion for now by @pandu-k

• Related Python client changes (link commit/PR here)
  none

• Related documentation changes (link commit/PR here)
  pending

• Other information:

• Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes/features)
• Docs have been added / updated (for bug fixes / features)

[pandu-k]

There is no explicit Array type, in OS: https://www.elastic.co/guide/en/elasticsearch/reference/7.17/array.html

[pandu-k]

To test (for Image index and reg. index):
- Lexical search of fields (as a searchable and non searchable attr) [DONE]
- Filtering (lexical and non lexical search) [DONE]
- Add-docs: check the document structure (list appears in chunks, but has no dedicated chunks)

[pandu-k]

py-marqo PR: marqo-ai/py-marqo#58
docs preview: https://gh-previews.marqo.pages.dev/0.0.13/Advanced-Usage/document_fields/#array

[pandu-k]

Unit tests passed: https://github.com/marqo-ai/marqo/actions/runs/4154756600