Expose option images to views.

Issue Summary

Based on my limited understanding of the views api, I believe you hook your module into views by letting it view the data in your modules table.

This module does not create any tables. The data association for images to options is based on the name of the file that is saved to the files table: option_image_5_2_4 which corresponds to node 5, attribute 2, option 4.

I believe for this module to hook into views, it needs to create its own table to store this data instead of using naming convention. Someone with more views experience can add more here if I'm wrong.