Repository: next.js
Issue: Cannot use 2 font families
Labels: bug,Font (next/font)

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
Platform: macOS
Version: Big Sur
Binaries:
Node: 16.16.0
npm: 8.11.0
Yarn: 1.22.17
Relevant packages:
next: 13.1.1
eslint-config-next: 13.4.4
react: 18.2.0
react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Font optimization (next/font)

### Link to the code that reproduces this issue or a replay of the bug

https://stackblitz.com/edit/nextjs-fonts

### To Reproduce

We are using below config where the first one is for latin characters in english and the second one is for arabic characters.

```
import localFont from 'next/font/local';

export const myProxima = localFont({
  variable: '--my-proxima',
  display: 'swap',
  adjustFontFallback: false,
  src: [
    {
      path: './Proxima-Nova-Bold.woff2',
      weight: '700',
      style: 'normal',
    },
    {
      path: './Proxima-Nova-Light.woff2',
      weight: '300',
      style: 'normal',
    },
    {
      path: './Proxima-Nova-Regular-Italic.woff2',
      weight: '400',
      style: 'italic',
    },
    {
      path: './Proxima-Nova-Regular.woff2',
      weight: '400',
      style: 'normal',
    },
    {
      path: './Proxima-Nova-Semibold.woff2',
      weight: '600',
      style: 'normal',
    },
    {
      path: './Proxima-Nova-Thin-Italic.woff2',
      weight: '200',
      style: 'italic',
    },
    {
      path: './Proxima-Nova-Thin.woff2',
      weight: '200',
      style: 'normal',
    },
  ],
});

export const myGESS = localFont({
  variable: '--my-gess',
  display: 'swap',
  adjustFontFallback: false,
  src: [
    {
      path: './GESSTwoLight.woff',
      weight: '200',
      style: 'normal',
    },
    {
      path: './GESSTwoLight.woff',
      weight: '300',
      style: 'normal',
    },
    {
      path: './GESSTwoLight.woff',
      weight: '400',
      style: 'normal',
    },
    {
      path: './GESSTwoMedium.woff',
      weight: '600',
      style: 'normal',
    },
    {
      path: './GESSTwoBold.woff',
      weight: '700',
      style: 'normal',
    },
  ],
});

```

### Describe the Bug

Normally we can just rely on font-face to automatically switch the font to the one which is able to handle all characters in a displayed string.
After starting to use next/font we need to pass the prop `adjustFontFallback: true` as otherwise the english font would always over take the arabic font as the fallback will be always applied.
Similarly if we don't add it on arabic we would start displaying arabic numbers instead of latin numbers which in our use case is also unconventional.

For now we are handling it via adjustFontFallback but that defeats the purpose of improving our CLS.

Same issue was reported here but closed: https://github.com/vercel/next.js/issues/44825

### Expected Behavior

Able to add a fallback which acts the same way as the font that was assigned so that we can handle such cases via normal font-face behavior of the browser to use the font-family which is able to handle all characters of string.

### Which browser are you using? (if relevant)

Chrome 113.0.5672.126

### How are you deploying your application? (if relevant)

Custom