fix(flexsearch): separate chain of calls into statements

[steven-mathew]

This makes the search bar continue to work when many (2000+) pages are added.

Summary

This adjusts the way in which the search index is built so that the call stack is not exceeded on some browsers (see #738 for browser compatibility). I'm not familiar with Hugo templating so if there's a preferred way, we can go that route!

Basic example

Previously, the compiled template would add to the array index by chaining .add() calls.

index.add(
{
  id: 3,
  href: "/docs/prologue/doc1/",
  title: "doc1",
  description: "Doks comes with commands for common tasks.",
  content: ""
})
.add(
{
  id: 4,
  href: "/docs/prologue/doc10/",
  title: "doc10",
  description: "Doks comes with commands for common tasks.",
  content: ""
})
.add(
{
  id: 5,
  href: "/docs/prologue/doc100/",
  title: "doc100",
  description: "Doks comes with commands for common tasks.",
  content: ""
})
...

Now, this PR would make the resulting template add to index without chaining, something like:

index.add(
  {
    id: 3,
    href: "/docs/prologue/doc1/",
    title: "doc1",
    description: "Doks comes with commands for common tasks.",
    content: ""
  }
);
index.add(
  {
    id: 4,
    href: "/docs/prologue/doc10/",
    title: "doc10",
    description: "Doks comes with commands for common tasks.",
    content: ""
  }
);
index.add(
  {
    id: 5,
    href: "/docs/prologue/doc100/",
    title: "doc100",
    description: "Doks comes with commands for common tasks.",
    content: ""
  }
);
...

Motivation

Closes #738

Checks

• Read Create a Pull Request
• Supports all screen sizes (if relevant)
• Supports both light and dark mode (if relevant)
• Passes npm run test

[h-enk]

Thanks for this! Will take a closer look and do some testing later.

[h-enk]

Tested + verified. Your solution is totally fine with me. Thanks for this!