Fix MSAA when using rendering pipelines (#1282)

Brings in changes from
BabylonJS/Babylon.js#14292 as part of the
package version update.

The main fix was a misunderstanding of the `BGFX_TEXTURE_MSAA_SAMPLE`
flag in bgfx and how textures are resolved. Thanks to @sebavan for
explaining to me how texture resolving works.

Author: bghgary

Apps/package-lock.json

@@ -6,11 +6,11 @@
     "getNightly": "node scripts/getNightly.js"
   },
   "dependencies": {
-    "babylonjs": "^6.14.2",
-    "babylonjs-gltf2interface": "^6.14.2",
-    "babylonjs-gui": "^6.14.2",
-    "babylonjs-loaders": "^6.14.2",
-    "babylonjs-materials": "^6.14.2",
+    "babylonjs": "^6.20.2",
+    "babylonjs-gltf2interface": "^6.20.2",
+    "babylonjs-gui": "^6.20.2",
+    "babylonjs-loaders": "^6.20.2",
+    "babylonjs-materials": "^6.20.2",
     "chai": "^4.3.4",
     "jsc-android": "^241213.1.0",
     "mocha": "^9.2.2",

Apps/package.json

@@ -1107,12 +1107,7 @@ namespace Babylon
         auto flags = BGFX_TEXTURE_NONE;
         if (renderTarget)
         {
-            flags |= BGFX_TEXTURE_RT;
-
-            if (samples > 1)
-            {
-                flags |= BGFX_TEXTURE_MSAA_SAMPLE | RenderTargetSamplesToBgfxMsaaFlag(samples);
-            }
+            flags |= BGFX_TEXTURE_RT | RenderTargetSamplesToBgfxMsaaFlag(samples);
         }
         if (srgb)
         {