fix(schema): fix schema generation with multiple Enums having the same name

[PrettyWood]

Change Summary

Two Enums with the same name were overlapping because we were not using the "long name" (module name + __name__ (soon __qualname__ but that's another PR...cf #2170))
Since we were already computing the long names for both models and enums, the fix is trivial!

Related issue number

closes #1857

Checklist

• Unit tests for the changes exist
• Tests pass on CI and coverage remains at 100%
• Documentation reflects the changes where applicable
• changes/<pull request or issue id>-<github username>.md file added describing change
  (see changes/README.md for details)

[codecov]

Codecov Report

Merging #2226 (d0a0142) into master (3496a47) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master     #2226   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines         4121      4121           
  Branches       829       829           
=========================================
  Hits          4121      4121           

Impacted Files	Coverage Δ
pydantic/schema.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3496a47...d0a0142. Read the comment docs.

[samuelcolvin]

looks good to me, any chance this is going to cause a breaking change with schema changing in a breaking way for some people?

[PrettyWood]

IMO no. It doesn't change anything if there is a single name. The only impact is when there were conflicting names. So if it breaks something for someone it should highlight the issue that there were in fact multiple enums with the same name and fixing it should be trivial

[samuelcolvin]

thank you.

[mnixry]

I hope this fix can be released soon