AVRO-3411: Support VSCode devcontainer

[zcsizmadia]

Make sure you have checked all steps below.

Jira

• My PR addresses the following Avro Jira
  • https://issues.apache.org/jira/browse/AVRO-3411
  • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Tests

• My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Documentation

• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain Javadoc that explain what it does

[iemejia]

Thanks for bringing this one in @zcsizmadia !
I let some minor comments.

[iemejia]

Do we really need this? Specially all the 'auto', isn't auto the default?
Should we cover the formats we don't care about e.g. doc/pdf/rtf?
I don't remember where we are towards line endings. @RyanSkraba maybe?

[RyanSkraba]

There was a discussion on this about AVRO-3150 -- some tests were failing due to an overzealous checkstyle check IIRC.

Is there something that fails if this .gitattributes isn't present? I'm not familiar with all the attributes, I admit! What does diff and astextplain do?

I have no objection to enforcing that script files are CRLF/LF no matter where they're checked out!

[RyanSkraba]

I would love to take a closer look at this -- to be honest, I've always kind of disliked the uberjar, but this is a pretty neat feature!

[zcsizmadia]

I heavily use devcontainer for other multi language/multi platform projects. AFAIK VSCode is the most used editor for such projects.

I like the fact that e.g. when I developed the extra codecs for C# , I could just generate the interop data for all the other languages, so my C# tests were running againsta ll the compression codecs generated by the other languages.
Just simply ran ./build.sh interop...generate, without knowing anything about Ruby, PHP, or Java.

[zcsizmadia]

It is possible to have devcontainer config for each languages seperately, however since the dockerfile has all the tools and all the project depend on each other via the interop tests, I thought having full container setup for the whole project (based on the already existing dockerfile) makes more sense

[iemejia]

LGTM

I validated it in a local container on mac and it works.

I had some issues with the C# project import but we can fix those afterwards, merging this is great for the benefit of everyone who can now contribute in an easy reproducile way. Excellent work @zcsizmadia !