prod-230

remove chatbox while broken

prod-229

Merge pull request #198 from couchbase/DOC-14221-move-to-ask-ai

DOC-14221 move to ask ai

prod-228

Merge pull request #201 from couchbase/DOC-14254-nav-config-expandHea…

docsearch-upgrade-spike-1

Docsearch update to recent instantsearch widget

DOC-14254-nav-config-expandHeaderLevels-2

DOC-14254 fix expandHeader logic

DOC-14221-move-to-ask-ai-NaN

DOC-14221 fix some descriptions

DOC-14254-nav-config-expandHeaderLevels-1

DOC-14254 expandHeaderLevels in playbook site.keys.navGroups

Instead of having to configure `:page-nav-header-levels:` in every antora.yml, we can just update in the playbook

```
site:
  keys:
    navGroups:
       [
         { "title": "Capella", "startPage": "home::cloud.adoc", "components": ["cloud", "app-services", "ai", "analytics"], "expandHeaderLevels": 1 },
         ...
         { "title": "Develop", "startPage": "home::developer.adoc",
             "expandHeaderLevels": 1,
             "subGroups": [
               {
                 "title": "Operational SDKs",
        ...
```

prod-227

Merge pull request #199 from couchbase/refactor-templates

Refactor templates

prod-226

Merge pull request #199 from couchbase/refactor-templates

Refactor templates

DOC-14254-page-nav-header-levels-error-2

DOC-14254 fix logic of nav header levels

The logic switched based on the number of nav files available.
This broke components where the landing page (defined in docs-site, with a single nav)
referred to a component such as SDK which has multiple navs for different components.

Capella used to have a single one, but has evolved to have multiples in left nav,
causing some oddities.

This change will require setting the correct `:page-nav-header-levels: 1` to
all repos in SDK, as well as the landing pages in docs-site (cloud.adoc,
sdk.adoc, analytics-sdk.adoc, and developer.adoc)