Update: Add JSDoc documentation to core view classes (fixes #854)

[joe-replin]

Fixes #854

Update

• Added @file, @module, and @class/@classdesc/@extends block to contentObjectView.js, including @fires tags for all lifecycle events and full JSDoc for render(), remove(), and renderTo()
• Added @file, @module, and @class block to pageView.js; documented remove() override explaining $pageLabel cleanup
• Added @file, @module, and @class block to menuView.js
• Added @file, @module, and @class block to menuItemView.js
• Added @file, @module, and @class block to articleView.js
• Added @file, @module, and @class block to blockView.js
• Added @file, @module, and @class block to componentView.js; added @returns {void} to setupInviewCompletion()
• Added @file, @module, and @class block to questionView.js with full documentation of the submit pipeline, feedback, reset, and correct-answer reveal methods; documented all @protected override hooks and all @deprecated compatibility-layer methods with @returns types and {@link} cross-references

Testing

1. Run grunt dev and confirm no build errors are introduced by the JSDoc changes
2. Run the JSDoc generator and confirm all eight files appear in the output with correct module paths and class entries
3. Open each file in an editor with JSDoc support (e.g. VS Code) and confirm hover tooltips display the new descriptions, @param types, and @deprecated warnings on the compatibility-layer methods
4. Confirm log.deprecated() runtime calls remain intact in questionView.js by opening a course in the browser, triggering a legacy question component, and verifying the deprecation warnings appear in the console