Flag using "build" instead of "built"

**The Error**
It's very common for people to use "build" when they mean "built". Especially nonnative speakers but I have a feeling native speakers are responsible for some of these too.

The obvious context is after forms of the copula "be":

**Examples:**
1. Electron is **build** on Node/Chromium and JavaScript.
2. This Project is **build** with React JS to build the UI of the project.
3. RuntimeError: use_libuv was requested but PyTorch was **build** without libuv support
4. [How DocFlow is **build**
5. Streaming engine cannot be **build** for pyodide
6. Macro utilities that Chimney is **build** upon.
7. New Front-End Checklist website and rules are currently being **build**!
8. In my case the parsers were **build** using MinGW toolchain.
9. I've **build** an ipa package from my iOS app project. After open the .ipa file with zip. I find that here's so many swift support dynamic libraries.

**Potential Edge Cases**

There are quite a few:

- Where is **Build Creator** for Linux?
- The future of defaulting to Bloop for **build tools** that can also be build servers.
- For example this would be **build 123**
- Is **build** still needed if I am building an application, not a JS library?
- quarkus.native.builder-image.pull is set to 'missing' but it is **build time** fixed to 'always'
- If I try to export the project from command line but there is **build error**
- Is **build file** auto-reload a sensible default?
- Where is **build.sh** script?
- Success return code after there were **build errors**

Start by reviewing the examples and the existing grammar rules for forms of “be” and perfect-tense uses of “build.” Verify that the intended “built” corrections work in passive constructions and “I've build,” while leaving nouns, compounds, commands, filenames, and other build-related terms unchanged.

Written by the indexing model from the issue text.