add visual aids to indicate exhaustion of options

When I scroll all the way down to `revert`, it cycles down to `feat`. I can't easily figure out if I've exhausted all the options

This is from the perspective of a new user.

I would love to see one of two changes:

## Option One

Pressing down at the bottom places the cursor with `feat` at the _top of the list_. Currently it selects `feat` but without doesn't indicate that it's the end of available options.

```
? Select the type of change that you're committing: (Use arrow keys)
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
chore: Other changes that don't modify src or test files
❯ revert: Reverts a previous commit
```
```
? Select the type of change that you're committing: (Use arrow keys)
❯ feat: A new feature
fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
```

## Option 2

Add a blank line at the end to signify we're at the end of possible options.

```
? Select the type of change that you're committing: (Use arrow keys)
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
chore: Other changes that don't modify src or test files
❯ revert: Reverts a previous commit
```

```
? Select the type of change that you're committing: (Use arrow keys)
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
chore: Other changes that don't modify src or test files
revert: Reverts a previous commit

❯ feat: A new feature
fix: A bug fix
docs: Documentation only changes
```

Aucun fichier source ni test n’est indiqué. Commencez par le code CLI qui affiche l’invite de sélection du type de commit, puis vérifiez comment le défilement de `revert` vers `feat` est géré. C’est terminé lorsque l’interface indique visiblement que les options disponibles sont épuisées.

Rédigé par le modèle d'indexation à partir du texte de l'issue.