Anti-aliasing(with vector graphics) failed with Winding Fill

### Description
Anti-aliasing with vector graphics seems to be not working. Though it looks acceptable on 1080x1920 rendering results, it appears bad on the preview window. Things become worse when mobjects are small(e.g. thin stroke in an 'x' character).


The issue seems ubiqutous among VMobject, especially among VMobject with dense points like string and tex.

### How is this caused
I checked code and I think its caused by shader code changes. Now in the fragment shader of quadratic_bezier_fill(after winding fill was introduced, I think?), it no longers uses `smoothstep` to calculate the fragment alpha for a **smooth border**, which was the mechanism in vector graphics that did the anti-aliasing. Not fragments are `discard` when `Fxy == 0` directly. I'm not sure whether this issue can be fixed, or is this intended?

### Platform
My platform information: I'm on win10, python 3.9. I didn't encounter the problem until I upgrade across the recent commits(where winding-fill was introduced and rendering was refactored into shader wrappers), and the issue exists till the latest commits available(~Feb 16) on github.

O issue aponta para o fragment shader quadratic_bezier_fill, onde o anti-aliasing via smoothstep foi substituído por uma condição discard. Comece examinando o código do shader no repositório manim, provavelmente em um diretório de shaders ou rendering. Procure commits recentes que introduzem winding fill. Teste a renderização de VMobjects pequenos para ver o aliasing. É necessário entender shaders OpenGL e renderização de gráficos vetoriais para propor uma correção.

Escrita pelo modelo de indexação a partir do texto da issue.