revert(VTextField): partial revert of #12554

[MajesticPotatoe]

Description

Partial revert of #12554.

Motivation and Context

#12554 introduced unintended regression of the functionality of hide-details="auto"
resolves #12755

How Has This Been Tested?

visual | jest

Markup:

<template>
  <v-container>
    <v-checkbox
      v-model="hasMessage"
      label="Show Message"
    />
    <v-checkbox
      v-model="hideDetails"
      label="hideDetails"
    />
    <v-row>
      <v-col>
        <v-text-field
          label="Test Message Animation"
          :hide-details="d"
          :error="hasMessage"
          :messages="hasMessage ? 'Message to see' : undefined"
        />
      </v-col>
      <v-col>
        <v-radio-group
          :error="hasMessage"
          :messages="hasMessage ? 'Message to see' : undefined"
          hide-details="auto"
        >
          <v-radio label="Test" />
        </v-radio-group>
      </v-col>
    </v-row>
  </v-container>
</template>

<script>
  export default {
    data: () => ({
      hasMessage: false,
      hideDetails: false,
    }),
    computed: {
      d () {
        return this.hideDetails ? this.hideDetails : 'auto'
      },
    },
  }
</script>

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Improvement/refactoring (non-breaking change that doesn't add any features but makes things better)

Checklist:

• The PR title is no longer than 64 characters.
• The PR is submitted to the correct branch (master for bug fixes and documentation updates, dev for new features and backwards compatible changes and next for non-backwards compatible changes).
• My code follows the code style of this project.
• I've added relevant changes to the documentation (applies to new features and breaking changes in core library)