Optimize how code strings are built up to reduce the library size

As part of the nanoColor project, we have been trying to reduce the size of the library. Currently nanoColor is between 1.5-3 MB, depending on the platform and compiler flags but the goal is to get it down to 1 MB or less.

As we have profiled where the size of the existing library comes from, we noticed that there is a lot of size coming from modules that create code. For example, all the modules that build shader code for various GPU languages are among the largest. Another example is the way Exception message strings are built. All of this uses a pattern which is nice to read in the code but which creates a lot of temporary string objects that bloats the library size.

This proposal is to find a better way to build up these long strings from components that is both easy to read in the code but which is much more efficient in terms of the size of the library.

首先分析构建 GPU 语言着色器代码的模块，以及 issue 中描述的异常消息字符串构造过程。比较组装长字符串的方法，然后验证库的大小是否在不损失可读性的情况下缩减至所述目标，即 1 MB 或更小。

由索引模型根据 Issue 内容生成。