Adding [1] to an INLINE pragma causes GHC to OOM without a good reason
## Summary
This example has `{-# INLINE [1] interpretAst #-}` and GHC OOMs on it when compiling the very same module (of 400 lines) where the pragma resides. I don't see a good reason it should OOM, with the possible exception of the typing plugins that are used in the module causing the OOM. I think plugins causing the OOM is unlikely, because no other pragmas trigger the OOM and I'm not aware of such pragmas interacting with the plugins (typing plugins probably run earlier than the pragmas are taken into account?). Also, changing typing plugins versions didn't help. I've tried the following pragmas
```
{-# INLINEABLE interpretAst #-}
{-# INLINEABLE [1] interpretAst #-}
{-# INLINEABLE [99] interpretAst #-}
{-# NOINLINE interpretAst #-}
{-# NOINLINE [1] interpretAst #-}
{-# NOINLINE [99] interpretAst #-}
{-# INLINE interpretAst #-}
{-# INLINE [1] interpretAst #-}
{-# INLINE [99] interpretAst #-}
no pragma
```
and of these only `INLINE [1]` triggers the OOM.
Edit: `INLINE [0]` OOMS and `INLINE [2]` compiles fine.
Edit2: Neither `INLINE [~0]` nor `INLINE [~1]` OOMs. Both `INLINE [~2]` and `INLINE [~99]` OOM.
## Steps to reproduce
```
git clone git@github.com:Mikolaj/horde-ad.git
cd horde-ad
git checkout repro-inline-OOM
rm -f cabal.project.local
cabal update
cabal build lib:horde-ad --enable-optimization --allow-newer -w /home/mikolaj/r/ghc.9.14/ghc/_build/stage1/bin/ghc
```
The example is not minimised. In particular, the ghc-options in the .cabal file are very non-standard and cause compiling to take longer than is usual (but not to OOM, normally).
## Expected behavior
Compiles.
## Environment
* GHC version used: 9.14.1, HEAD with !15389
Optional:
* Operating System: Ubuntu
* System Architecture: amd64
issue