Update WARNINGS.md (#1353)

* Update WARNINGS.md

Include a link to a more detailed explanation of how to handle accumulating dependencies before constructing a depset.

* Updating warnings.textproto and regenerating WARNINGS.md

---------

Co-authored-by: Tim Malmström <[email protected]>
Co-authored-by: Tim Malmström <[email protected]>

Bug fix. Correctly identify expressions using &=, ^=, >>=, and <<= as…

… assignment statements when parsing BUILD files. (#1357)

* Add files via upload

Correctly include &=, ^=, >>=, <<= as assignment statements when parsing BUILD files.

The Starlark grammar reference (https://github.com/bazelbuild/starlark/blob/master/spec.md#grammar-reference) identifies all of these as assignment statements, but the parser doesn't include them in the list, probably an old oversight.

This fixes issue #1330.

* Update warn_control_flow_test

This change adds no-effect tests for &=, ^=, >>=, and <<= to ensure they are recognized as having an effect.

Fix a potential NPE (#1331)

Fix load placement for files with docstring and copyright header (#1329)

Also add missing setup calls for other tests.

Fix and improve float formatting (#1309)

* Don't break `12e+34` into `12e + 34`

* Better implementation

* Normalize floats

Fix failing tests on CI (#1317)

* Update the checked in protos
* Bump the dependencies
* Don't test on Ubuntu 18.04
* Disable failing tests on Windows CI

Bump google.golang.org/protobuf from 1.25.0 to 1.33.0 (#1251)

* Bump google.golang.org/protobuf from 1.25.0 to 1.33.0

Bumps google.golang.org/protobuf from 1.25.0 to 1.33.0.

---
updated-dependencies:
- dependency-name: google.golang.org/protobuf
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>

* Update go.sum

* Update generated files

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Vladimir Moskva <[email protected]>

Add support for `*.MODULE.bazel` files (#1266)

After bazelbuild/bazel#22075, these are the
files that can be `include()`ed into `MODULE.bazel` files and should be
formatted and edited just like them.

buildozer: correctly substitute custom string attrs (#1246)

Stricter formatting of load statements (#1244)