[#3304] Redesign Vuestic landing

[RVitaly1978]

Description

close #3304
close #3347

• update landing page
• update overview page
• fix landing.vue and default.vue nuxt layouts

screenshots

Screen.Recording.2023-04-17.at.19.47.39.mov

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Improvement/refactoring (non-breaking change that doesn't add any feature but make things better)

[m0ksem]

• contrast issue in partners block:

• IE icons seems inappropriate

While we have blue as accent color, it feels strange to have purple icons

Hand drawn icons feel inappropriate when all other design looks formal.

Text also not relevant. IMO "Support modern browsers" mean nothing, wondering if there are frameworks that support only old browsers lol. "No IE, sorry" also old and must be removed because it makes no sense (every vue3 framework do not support IE11 and it is not modern browser). I would change it to "responsive" only.

As a developer I will be interested in Developer Experience, SSR support, Keyboard Navigation and integration with other things like AgGrid, Tailwind, UnoCss, (maybe Laravel, rich text editors - we don't have this for now), etc. I change features list to:

Accessible & keyboard navigation support
- SSR friendly
- Focused on DX
- Integration with i18n, tailwind and more

• "Customize everything" "Get started" button should redirect to some page related to customization. Perhaps we need some "Customization guide" page.

• Overall, "Features" and "Customize Everything" look so much different from other sections.

Btw, first section looks perfect!

[m0ksem]

@zvenigorodskaia, we must merge this PR in develop when it is completed. If you're going to review this, please, run project locally. Otherwise, the incomplete landing page will appear in production with tiny releases someday. For example, I've just fixed the form demos and if we merge this PR before, it would have ended up in production.

[m0ksem]

Must be h2, cuz it is a header of sponsors section (even if it smaller)