chore(survey): change copy (mdn#6526)

Merge pull request mdn#6524 from mdn/support-multiple-surveys

feature(surveys): support multiple surveys

fix: update style for short surveys (mdn#6497)

* fix: update style for short surveys

Update the style for the short survey component.

* ensure foreground color is $mdn-color-neutral-90 for text and close icon

chore(banner): disable current banner (mdn#6510)

fix: remove padding from live sample frame (mdn#6506)

Remove padding from live sample frame to address the problem highlighted in the following discussion:
https://github.com/orgs/mdn/discussions/127

fix(search): hide results unless focused (mdn#6477)

chore(tsconfig): move compilerOptions up (mdn#6489)

Consolidates our `tsconfig.json` files by moving some 
common `compilerOptions` into our root `tsconfig.json`:
- `allowSyntheticDefaultImports = true`
- `esModuleInterop = true`
- `forceConsistentCasingInFileNames = true`
- `moduleResolution = node`
- `resolveJsonModule = true`
- `skipLibCheck = true`

Exceptions:
- `/markdown/tsconfig.json` needs `esModuleInterop = false`.
- `/client/pwa/tsconfig.json` doesn't extend `/tsconfig.json`.

chore(macros/JsSidebar): update zh-CN strings (mdn#6498)

fix(build/spas): replace global variable (mdn#6491)

Avoids that building the Contributor Spotlight for
the next locale replaces data for the previous one.

Co-authored-by: Schalk Neethling <[email protected]>

Make Specifications work as expected with multiple BCD queries (mdn#6465

)

* Make Specifications work as expected with multiple BCD queries

Without this change, if there are multiple BCD features (array value in
browser-compat), the Specifications section isn’t populated as expected.

* Further update Specifications population to handle multiple BCD queries

Some features — e.g., css.properties.justify-content — have no compat
data themselves but have subfeatures with compat data. In the case
where we’re processing a browser-compat value which is an array, unless
we explicitly check for the __compat-less-feature-with-subfeatures case,
and handle it, we can end up with expected specifications being entirely
missing from the rendered Specifications section.

So this change adds handling for that case.