Rake task registers database path for rake-cleaning

Rake ships with clean and clobber tasks out of the box.
Now the audit Task can be (optionally) registered for cleaning.

It defaults to off so no change from current behavior. If opted-in, the
audit-database path is added to rake's CLOBBER collection.

Clean is meant to remove temporary and generated files that are the
result of "normal" application runs.
Clobber is intended to be a more exhaustive clean that returns the
application's state to a "fresh cloned" state.

With these conventions, the ruby advisory db fits more cleanly (ha) into
the "clobber" category.

Author: jasonkarns

lib/bundler/audit/task.rb

@@ -12,8 +12,8 @@ class CommandNotFound < RuntimeError
       #
       # Initializes the task.
       #
-      def initialize
-        define
+      def initialize(clean: false)
+        define(clean:)
       end
 
       #
@@ -88,7 +88,9 @@ def update
       #
       # Defines the `bundle:audit` and `bundle:audit:update` task.
       #
-      def define
+      def define(clean:)
+        register_clean if clean
+
         namespace :bundle do
           namespace :audit do
             desc 'Checks the Gemfile.lock for insecure dependencies'
@@ -109,6 +111,13 @@ def define
         task 'bundler:audit:check'  => 'bundle:audit:check'
         task 'bundler:audit:update' => 'bundle:audit:update'
       end
+
+      def register_clean
+        require 'rake/clean'
+        require 'bundler/audit/database'
+
+        CLOBBER.include Bundler::Audit::Database.path
+      end
     end
   end
 end