Complex parameter types

Some parameters may contain `.` in their names. For example,

``` js
/**
* Sets cookie to this wrapper.
* @param {Object} cookieSetup Cookie setup object.
* @param {string} cookieSetup.key Cookie key.
* @param {string} cookieSetup.value Cookie value.
* @param {number?} cookieSetup.maxAge Max cookie age in seconds.
* @param {Date?} cookieSetup.expires Expire date.
* @param {string?} cookieSetup.path URI path for cookie.
* @param {string?} cookieSetup.domain Cookie domain.
* @param {boolean?} cookieSetup.secure Is cookie secured.
* @param {boolean?} cookieSetup.httpOnly Is cookie HTTP only.
* @returns {string} Cookie setup string.
*/
CookieWrapper.prototype.set = function (cookieSetup) {
...
}
```

Currently these complex types are ignored. They should instead be parsed and added to output.

Find the code that parses JSDoc @param entries and produces TypeScript definitions, then compare its handling of simple parameters with the dotted names in the CookieWrapper example. Update the parsing behavior so nested parameter names and their types appear in the output, and verify the generated result against the example.

Written by the indexing model from the issue text.