Fix albedo value wraparound in Compatibility render mode
Using the Compatibility renderer results in wrapped albedo values if a custom shader returns albedo values outside the expected range of [0,1].
This commit fixed this issue by clamping the albedo value to [0,1] right after the custom shader is executed.
Fixes #91919