Empty filter objects for new/unconfigured filters are incomplete

When a new filter (not yet in the database) is loaded on the filter configuration page, a default filter object is constructed to represent it; among other things, this is passed on to the 'settings callback' of that filter.

This object is not complete - among other things, it is missing the name of the filter itself. This information can be useful; for example, I am currently trying to port a D6 module to D7 which provides two filters that are similar enough that they share a settings callback (but have slight differences, so need to always know which filter they are being called for). There are ways around this, but the simplest is to fix this issue, which is a bug because the mock filter object should not be missing properties that would otherwise be passed in after it has made its way into the database.