Incorrect raw value for "loose" custom field filter logic

[jeremystretch]

Environment

• Python version: 3.6.9
• NetBox version: 2.9.9

Steps to Reproduce

1. Create a custom field with its filter logic set to "loose"
2. Inspect the column's value in the database table (extras_customfield.filter_logic)

Expected Behavior

The value should read "loose".

Observed Behavior

The value reads "integer".

This is due to an error in database migration 0029_3569_customfield_fields under the extras app, which incorrectly converts the old numeric representation to the slug value "integer" instead of "loose". (This was due to a copy/paste error when constructing the migration.)

It's worth noting that this error doesn't actually inhibit functionality. However, with REST API support being introduced for custom fields in v2.10 (#5274), the value needs to be corrected.