feat(VAutocomplete): port to v3

[johnleider]

Description

Port v-autocomplete to v3.

TODO

• fix no-data-text
• add the following properties
  • deletable-chips (renamed to closable-chips)
  • eager
  • hide-no-data
  • auto-select-first (pending keyboard support)
  • cache-items (removed)
  • disable-lookup (v-select only)
  • hide-spin-buttons (not relevant to v-autocomplete)
  • no-filter (pending update to filter composable)
  • small-chips (using density

KNOWN ISSUES

• selection during filter when using the multiple prop drops missing items

How Has This Been Tested?

n/a

Markup:

<template>
  <v-app>
    <v-main>
      <div class="ma-4 pa-4">

        <div>
          Search: <pre>{{ JSON.stringify(search, null, 2) }}</pre>
        </div>

        <div>
          Model: <pre>{{ JSON.stringify(model2, null, 2) }}</pre>
        </div>

        <br>
        <br>

        <v-autocomplete
          v-model:search="search"
          v-model="model2"
          label="Autocomplete"
          :items="items"
        />

        <!-- <v-select
          v-model="model"
          label="Select"
          :items="items"
        />

        <v-text-field
          v-model="model"
          label="Textfield"
        /> -->
        <!-- <v-autocomplete
          key="what"
          v-model:search="search"
          v-model="model"
          open-on-click
          label="Autocomplete"
          :items="items"
          multiple
          clearable
        /> -->

        <!-- <v-select
          v-model="model"
          label="Select"
          :items="items"
          clearable
          multiple
        /> -->
      </div>
    </v-main>
  </v-app>
</template>

<script>
  export default {
    data: () => ({
      model: null,
      model2: 3,
      items: [
        // model 0 doesn't work at start
        // { title: 'One', value: 1 },
        // { title: 'Two', value: 2 },
        // { title: 'Three', value: 3 },
        // { title: 'Four', value: 4 },
        // { title: 'Five', value: 5 },
        // { title: 'Six', value: 6 },
        // { title: 'Foo', value: 1 },
        // { title: 'Bar', value: 2 },
        { title: 'Foobar', value: 3 },
        { title: 'Fizz', value: 4 },
        { title: 'Buzz', value: 5 },
        { title: 'Fizzbuzz', value: 6 },
      ],
      search: undefined,
    }),
  }
</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)