Inconsistent config.update_coded_value_map() in codebase

Branch to fix is here:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbwells/lp1091831_coded_value_map_function_fix

working/user/dbwells/lp1091831_coded_value_map_function_fix

This makes the schema version match the old upgrade, and adds a new upgrade file for anyone unlucky enough to have installed with the bad schema.

As it stands, while the logic is at least functional now, you will get an insert error if you 'add_only' something which is already there, rather than just a notice or warning, but maybe this is the intended behavior. If we decide we want to do something else, we will have to take that on separately.

Setting this high, since it is a simple fix and would be nice to get into 2.3.2.

Setting this to medium, since I don't think it is a show stopper, but I agree it should get in by the targeted milestones.

Thanks Dan! The upgrade applies cleanly to a 2.3.1 install, and I agree that it is a high priority for getting into 2.3.2.

Pushed to master and rel_2_3.