Describe the bug

Note: Please check the common issues on https://block.github.io/goose/docs/troubleshooting before filing a report

When Goose is executed using goose configure it misdocuments the configuration it utilizes suggesting that configuration is stored inside a single yaml file: config.yaml. This is incorrect and the entire ~/.config/goose directory is utilized to store configuration files including a permissions.yaml file that is updated in the following flow:

> goose configure

This will update your existing config file
  if you prefer, you can edit it directly at /Users/worldofzero/.config/goose/config.yaml

┌   goose-configure
│
◇  What would you like to configure?
│  Goose Settings
│
◇  What setting would you like to configure?
│  Tool Permission
│
◇  Choose an extension to configure tools
│  developer
│
◇  Choose a tool to update permission
│  developer__image_processor
│
◆  Set permission level for tool developer__image_processor, current permission level: Ask Before

The tools documentation should be updated to reflect its actual behavior.

To Reproduce
Steps to reproduce the behavior:

1. run goose configure
2. open ~/.config/goose/config.yaml in a text editor.
3. edit a tools permissions.
4. config.yaml has been unchanged.

Expected behavior
The file modified by Goose should be listed when updated in commands and documentation should document the goose directory not the config.yaml file.

This is wrong in a number of places within goose including goose configure, goose info and others.

Please provide following information:

• OS & Arch: macOS
• Interface: CLI
• Version: 1.9.2
• Provider & Model: databricks