Allowed values interface gives error when field in use

I tried to reproduce this issue in Drupal 10.2.2, but was not able to.
Steps followed

• Created a fresh Drupal 10.2.2 site.
• Added list field (Cardinality 1 & type 'Text') to aricle content type.
• Added 2 values - 'value-1' and 'value-2'
• Created an aricle, selected 'value-1' in list field. Published the article.
• Updated the field configuration of the list field.
• 'Value 1' is disabed as it is already used in article.
• Able to add a new value 'Value 3'
• Able to remove existing value 'Value 2'.

Adding tags as issue is not reproducible.

Drupal 10.2.4. I have a list field where all the values are present in the database. I am trying to simply update the label on one of the allowed values and receive the error. I am not trying to change the keys, only the display text, which should be possible.

In my case, in the function `options_field_storage_config_update_forbid` the `$field_storage` and `$prior_field_storage` arguments do not report the allowed values in the same format. The current values are in a completely different format. This appears to have additional related to form_state --

$allowed_values = $field_storage->getSetting('allowed_values'):
[
  'table' => [
     0 => [
       'item' => ['label' => 'Text value', key => 4],
       'weight' => "0",
     ],
    1 => [
      'item' => ['label' => 'Another text value', key => 3],
      'weight' => "1",
    ],
  ],
]

However the value returned for the prior values returns something completely different. This appears to be the current config storage, without the extra information.

$prior_allowed_values = $prior_field_storage->getSetting('allowed_values')
[
  4 => 'Text value',
  3 => 'Another text value',
]

Given what the values are, this code will never work as intended.

function options_field_storage_config_update_forbid(FieldStorageConfigInterface $field_storage, FieldStorageConfigInterface $prior_field_storage) {
  if ($field_storage->getTypeProvider() == 'options' && $field_storage->hasData()) {
    // Forbid any update that removes allowed values with actual data.
    $allowed_values = $field_storage->getSetting('allowed_values');
    $prior_allowed_values = $prior_field_storage->getSetting('allowed_values');
    $lost_keys = array_keys(array_diff_key($prior_allowed_values, $allowed_values));
    if (_options_values_in_use($field_storage->getTargetEntityTypeId(), $field_storage->getName(), $lost_keys)) {
      throw new FieldStorageDefinitionUpdateForbiddenException("A list field '{$field_storage->getName()}' with existing data cannot have its keys changed.");
    }
  }
}

After some further investigation, I believe https://www.drupal.org/node/3409364 could be behind what I was seeing. Once I upgraded to the latest version of the Field Permissions module, the behavior I was experiencing above (including the format of allowed values I was seeing in xdebug) is no longer present. I can no longer reproduce this issue.