Fix uninitialized constant HTTP::CookieJar by correcting load order in http_cookie_jar.rb

[tair-m]

This PR fixes a critical load order issue in http_cookie_jar.rb that causes msfconsole to crash with uninitialized constant HTTP::CookieJar or CookieJar is not a class when loading HTTP-based modules on environments using Ruby 3.3.0+ (such as recent Kali Linux rolling updates).

The newer Zeitwerk autoloader strictly enforces load order. Previously, http_cookie_jar.rb required http/cookie_jar/hash_store before the base http/cookie classes were loaded into memory, causing a crash during module parsing.

This change simply reverses the require order of the http-cookie gem files to load the base classes before the dependent storage classes.

Verification

List the steps needed to make sure this thing works

• Start msfconsole on a system running Ruby 3.3.0+ (e.g., latest Kali Linux).
• Run use exploit/unix/webapp/elfinder_php_connector_exiftran_cmd_injection (or any web module dependent on HttpClient).
• Verify the module loads successfully without the [-] The supplied module name is ambiguous: uninitialized constant HTTP error.
• Verify the info command works for the loaded module.

[adfoster-r7]

Release Notes

Fixes a crash when loading HTTP modules