fix: remove humanized descriptions from API Blueprint output

When parameters or attributes are defined without explicit descriptions,
the DSL auto-generates humanized descriptions (e.g., "option" -> "Option").
This change ensures these auto-generated descriptions are not included
in the API Blueprint output, providing cleaner documentation.

- Added humanize check to description_blank? method
- Updated RSpec tests to expect nil for auto-generated descriptions
- Fixes failing cucumber test for API Blueprint documentation

Author: bf4

lib/rspec_api_documentation/views/api_blueprint_index.rb

@@ -103,7 +103,8 @@ def fields(property_name, examples)
       # equals the name, I assume it is blank.
       def description_blank?(property)
         !property[:description] ||
-          property[:description].to_s.strip == property[:name].to_s.strip
+          property[:description].to_s.strip == property[:name].to_s.strip ||
+          property[:description].to_s.strip == property[:name].to_s.humanize
       end
     end
   end

spec/views/api_blueprint_index_spec.rb

@@ -142,7 +142,7 @@
           properties_description: "required, string"
         }, {
           name: "option",
-          description: 'Option',
+          description: nil,
           properties_description: 'optional'
         }]
         expect(post_route_with_optionals[:has_attributes?]).to eq false
@@ -158,7 +158,7 @@
         expect(posts_route[:attributes]).to eq [{
           required: false,
           name: "description",
-          description: 'Description',
+          description: nil,
           properties_description: "optional"
         }]
       end