Substrate: FPrimitiveViewRelevance::operator|= bitwise-ORs SubstrateUintPerPixel, inflating the per-pixel byte count and asserting under the blendable GBuffer

A crash can occur due to this check in Substrate.cpp when a material with 2 units and a material with 5 (20 bpp) uints are combined triggering :

check(CurrentMaxBytesPerPixel <= PlatformSettingsBytesPerPixel);

This can happen with Niagara vfx that has two or more emitters whose materials compile to Substrate uint counts that bitwise OR above the maximum, with blendable Substrate enabled and r.Substrate.ProjectGBufferFormat=0. The base class FMaterialRelevance operator|= function applies Max() to SubstrateUintPerPixel but the derived class FPrimitiveViewRelevance operator|= does not. When a material with 2 units and a material with 5 (20 bpp) uints are combined with | it results in 7 (28 bpp) which triggers the check(). A potential workaround is to add the missing Max():

	/** Bitwise OR operator. Sets any relevance bits which are present in either. */
	FPrimitiveViewRelevance& operator|=(const FPrimitiveViewRelevance& B)
	{
	 const uint32 LocalSubstrateUintPerPixel = SubstrateUintPerPixel;
     
	 // the class is only storing bits, the following avoids code redundancy
	 const uint8 * RESTRICT s = (const uint8*)&B;
	 uint8 * RESTRICT d = (uint8*)this;
	 for(uint32 i = 0; i < sizeof(*this); ++i)
	 {
	 *d = *d | *s; 
	 ++s;++d;
	 }

	 SubstrateUintPerPixel = FMath::Max(LocalSubstrateUintPerPixel, B.SubstrateUintPerPixel);
	 return *this;
	}

1. Blendable Substrate enabled with r.Substrate=True and r.Substrate.ProjectGBufferFormat=0.
2. Create a Niagara system with two or more emitters whose materials compile to Substrate uint counts that bitwise OR above the maximum (eg: one with 5 uints and one with 2 uints is what we're seeing).

Expected
The Emitter renders without crashing

Actual
The Editor crashes