fix(types): improve DeepPartial type for App Config

[julien1619]

🔗 Linked issue

Resolves #2221

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ 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

When strict Typescript check was added, some as const where added too, and the resulting config type was showing the default value as the only possible value. I think this is not what was intended, so I treated all the as const values as string in the config type.

📝 Checklist

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

[julien1619]

I noticed that the typecheck was failing. In fact the as const were added to send a valid value to the components which needs a strong type for some props. But the app.config.ts type is generated using only the default config.

It means that if I remove as const it improves the app.config.ts type, but breaks the typecheck of this module. So I tried adding the needed types to the default config (eg. ButtonSize, ButtonColor, etc.).

[ThibaultVlacich]

The source of the bug are the changes made in #1870

Fixing (or rolling back) the DeepPartial type util would be a better fix imo.

[benjamincanac]

It seems there is an issue in the Carousel.vue component, ui prop should be:

    ui: {
      type: Object as PropType<DeepPartial<typeof config> & { strategy?: Strategy }>,
      default: undefined
    }

[benjamincanac]

Fixed it on dev branch, can you merge it?

[julien1619]

Thanks @benjamincanac ! I've just rebased it, you can merge this PR I think :)