perf(schema): avoid duplicate get operations

[GalacticHypernova]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR saves the app that is gotten through the runtimeConfig $resolve async function and is used in place of the current 3 calls, resulting in a ~99.1% increase in performance.
Benchmark results (tested with the smallest possible timeout of 0 ms which would, in real time, likely take longer than that):

async function get(name){
        await new Promise((resolve)=>{
            setTimeout(()=>{},0)
            resolve(void 0)
        })
        return {baseURL:"",buildAssetsDir:"",cdnURL:""}
    }
    const val={}
    console.time("current")
    for (let index = 0; index < 100000; index++) {
       val.baseURL=(await get('app')).baseURL
       val.buildAssetsDir=(await get('app')).buildAssetsDir
       val.cdnURL=(await get('app')).cdnURL
    }
    console.timeEnd("current")
    const app = await get('app')
    console.time("PR")
    for (let index = 0; index < 100000; index++) {
        val.baseURL=app.baseURL
        val.buildAssetsDir=app.buildAssetsDir
        val.cdnURL=app.cdnURL
     }
     console.timeEnd("PR")

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[GalacticHypernova]

I will try to get the rest handled as well, but this was the thing that caught my eye the most.

[danielroe]

Nice 👌

[GalacticHypernova]

Could I request this PR to not be merged until I'm done fixing all of schema? Or is it fine if it gets merged in chunks?

[danielroe]

Oh, of course.

[GalacticHypernova]

Thank you!
I'll try to get this update ready by the end of the day.

[GalacticHypernova]

Looking at the webpack schema, I don't think making it as such is necessarily the most performant (for the same reason as this PR's title):

Can this be changed to something like this?

vue:  {
    $resolve: async (val, get) => {
        const vue = await get('vue')
        return defu(val, {
            transformAssetUrls: {
              video: 'src',
              source: 'src',
              object: 'src',
              embed: 'src'
            },
            compilerOptions: vue.compilerOptions,
            propsDestructure: Boolean(vue.propsDestructure),
            defineModel: Boolean(vue.defineModel)
        })
    }
}

Or would it have some kind of side effects? Because the same thing is done with the runtimeConfig:

It provides it from the app already so it doesn't have to get everything separately.