AVRO-3370: Allow complex types as names

[RyanSkraba]

Make sure you have checked all steps below.

Jira

• My PR addresses the following Avro Jira issues and references them in the PR title. For example, "AVRO-1234: My Avro PR"
  • https://issues.apache.org/jira/browse/AVRO-3370
  • 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

[netlify]

❌ Deploy Preview for avro-website-preview failed.

🔨 Explore the source changes: 0e38bbd

🔍 Inspect the deploy log: https://app.netlify.com/sites/avro-website-preview/deploys/62057c3dee33040007481e8a

[RyanSkraba]

Note -- we haven't really come to a consensus whether this is the right thing to do! https://lists.apache.org/thread/0wmgyx6z69gy07lvj9ndko75752b8cn2