Bazel 1.0 support

[aaliddell]

TODO:

• Update all dependencies
• Write release notes
• Replace rules_pip with rules_python
• Fix scala
• Fix rust

Closes #22, #14, #8, #10, #4, #23, #30

[plule-ansys]

bazel reports 5ec71602e9b458b01717fab1d37492154c1c12ea83f881c745dbd88e9b2098d8 for this one

[aaliddell]

Good spot, fixed, thanks

[plule-ansys]

For info, to get the C# generated code to be compatible with the nuget packages, I had to upgrade the grpc and protobuf packages to their latest versions:
google.protobuf: 3.10.1
grpc, grpc.core, grpc.core.api: 2.25.0

[aaliddell]

All languages except Scala are now working and at this point I'm considering bumping Scala support off the 1.0.0 target and disabling its tests in CI, as it's taking a massively disproportionate amount of my time to troubleshoot and subsequently delaying this merge. Scala support can be fixed in 1.1.0 if that's the decision made.

For info, to get the C# generated code to be compatible with the nuget packages, I had to upgrade the grpc and protobuf packages to their latest versions:
google.protobuf: 3.10.1
grpc, grpc.core, grpc.core.api: 2.25.0

I can't ever get the C# rules to work, let alone update the packages. Could you provide the changes as a PR based on this branch, so I can see if any tests work? Or see if #34 is the same?

[plule-ansys]

I can't ever get the C# rules to work, let alone update the packages. Could you provide the changes as a PR based on this branch, so I can see if any tests work? Or see if #34 is the same?

Unfortunately I can’t manage to build any of the examples here, and I’m pretty much lost in the whole .net frameworks, rules and nuget bazel files generations, so I’m not yet able to provide any proper PR. It’s the same kind of changes as #34. I’m trying to better understand the C# rules and nuget2bazel stuff, hopefully I’ll be able to contribute here.