Add properties in JSDoc generation on destructuring in javascript file

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section. --> ## Search Terms JSDoc destructuring generate property javascript <!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily --> ## Suggestion When you use the JSDoc generation on function using destructuring, it could list the properties. <!-- A summary of what you'd like to see added or changed --> ## Use Cases Avoid redundancy when writing code. It could be useful for Javascript files and Typescript files. <!-- What do you want to use this for? What shortcomings exist with current approaches? --> ## Examples Action: <img width="724" alt="capture d ecran 2018-10-17 a 15 21 44" src="https://user-images.githubusercontent.com/7831572/47089671-a04db100-d221-11e8-991b-8026474f9fc1.png"> Actual: <img width="542" alt="capture d ecran 2018-10-17 a 15 22 00" src="https://user-images.githubusercontent.com/7831572/47089698-acd20980-d221-11e8-9fab-f559210e0f3c.png"> Expectation: <img width="297" alt="capture d ecran 2018-10-17 a 15 22 48" src="https://user-images.githubusercontent.com/7831572/47089702-af346380-d221-11e8-8cd7-94e8010ec8cb.png"> ## Checklist My suggestion meets these guidelines: * [X] This wouldn't be a breaking change in existing TypeScript / JavaScript code * [X] This wouldn't change the runtime behavior of existing JavaScript code * [X] This could be implemented without emitting different JS based on the types of the expressions * [X] This isn't a runtime feature (e.g. new expression-level syntax)