Eagerly throw error if certain annotations are used on non-hardware types

[zyedidia]

Using forceName or DecodeTable on a non-hardware value now throws an error at the call-site instead of later in the pipeline when source locator information is no longer available. I will also open a separate pull request to backport this to 3.5.x with a deprecation warning instead of an error.

Contributor Checklist

• Did you add Scaladoc to every public function/method?
• Did you add at least one test demonstrating the PR?
• Did you delete any extraneous printlns/debugging code?
• Did you specify the type of improvement?
• Did you add appropriate documentation in docs/src?
• Did you state the API impact?
• Did you specify the code generation impact?
• Did you request a desired merge strategy?
• Did you add text to be included in the Release Notes for this change?

Type of Improvement

• code cleanup

API Impact

Using forceName or DecodeTable on a non-hardware value now throws an error at the call-site instead of later in the pipeline.

Backend Code Generation Impact

None.

Desired Merge Strategy

• Squash: The PR will be squashed and merged (choose this if you have no preference.

Release Notes

Using forceName or DecodeTable on a non-hardware value now throws an error at the call-site instead of later in the pipeline.

Reviewer Checklist (only modified by reviewer)

• Did you add the appropriate labels?
• Did you mark the proper milestone (Bug fix: 3.4.x, [small] API extension: 3.5.x, API modification or big change: 3.6.0)?
• Did you review?
• Did you check whether all relevant Contributor checkboxes have been checked?
• Did you do one of the following when ready to merge:
  • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
  • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

[jackkoenig]

Looks great, just 1 suggested improvement.