Remove 'indexes' from field base

Doesn't break anything for me and fixes things that weren't working before.

So, the problem with this patch is it causes all existing field base features to be marked as overridden.

This is different from #2419479: Remove 'foreign keys' from field base which was done in response to a change in core that was causing overrides.

We need a different solution to this that is backwards compatible and doesn't cause overrides. People shouldn't need to re-export features for something minor like this, and it's an issue for distributions that would need to be updated to re-export features.

There was also some functionality added recently to add an "ignore" list of keys, so maybe just adding indexes to that list would fix it. Look at the bottom of features.module for the implementation of the current ignore hook.

Set the status so this gets tested via the testbot

Patch from #7 works for me (applied together with patch from multifield-issue #2102265: Features integration, comment #32).

The patch from #7, together with patch #32 from #2102265: Features integration, work for me as well. I'm now able to deploy multifields from local to staging.

However, the feature that contains the base multifield and base subfields ends up being overridden, no matter how many times I try to revert. It was in 'Needs review' state at first, and then after reverting, it went into eternal 'Overridden' mode.

Here's the part the feature reports as being overridden:

'indexes' => array(
  'field_unit_length_value' => array(
    0 => 'field_unit_length_value',
  ),
  'id' => array(	
    0 => 'id',
  ),
),

I suspect that it has something to do with this issue, but not 100% sure. Any ideas how to get the feature to revert?

#7 didn't work for me for the reason described in #10, however this one does, had to fix a bug in _features_remove_ignores() as well.

Patch in #11 worked for me. Thanks MustangGB!

This is looking good now. Especially the bug fix to _features_remove_ignores(). I added an additional unset($value) which is just best practice after any foreach using &. Committed to 7c288b1.