Update docval to accept fully qualified class names

[rly]

Motivation

Follow-up to #1031 to allow a "type" argument in docval that is the name of a class to be linked to its documentation.

How to test the behavior?

Use this syntax for 'type' if you want to create a proper doc link to the LinkSpec class:

@docval({'name': 'spec', 'type': 'hdmf.spec.spec.LinkSpec', 'doc': 'the specification for the object to link to'})
    def set_link(self, **kwargs):
        pass

Checklist

• Did you update CHANGELOG.md with your changes?
• Does the PR clearly describe the problem and the solution?
• Have you reviewed our Contributing Guide?
• Does the PR use "Fix #XXX" notation to tell GitHub to close the relevant issue numbered XXX when the PR is merged?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.52%. Comparing base (fa18cc5) to head (d8f8d5b).
Report is 65 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev    #1036   +/-   ##
=======================================
  Coverage   88.51%   88.52%           
=======================================
  Files          45       45           
  Lines        9586     9594    +8     
  Branches     2725     2727    +2     
=======================================
+ Hits         8485     8493    +8     
  Misses        778      778           
  Partials      323      323           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[stephprince]

I think one more type that could be changed with this new docval behavior is 'type': 'HERD' to 'type':'hdmf.common.resources.HERD'? It would apply here, here, and here

otherwise looks good to me!

[rly]

I think one more type that could be changed with this new docval behavior is 'type': 'HERD' to 'type':'hdmf.common.resources.HERD'? It would apply here, here, and here

I am not sure how I missed that. Good catch!