Improve boot-time logging, configuration and middleware logistics

[delano]

User description

Improve boot-time logging, configuration and middleware logistics. Includes the following changes:

• Set default log level for middlewares to info (default for Logger in Ruby is debug, TIL)
• Simplify middleware logistics at start-time
• Simplify bootup sequence by refactoring the Onetime.boot! method
• Improve initialization performance and clarity
• Rename BUILD.yml to VERSION.yml for clarity
• Formatting changes
• Remove auto-loading debugger in dev + debug mode
• Delay requiring sentry until enabled (in dev)
• Remove legacy cli command (register_build)

These changes aim to simplify the middleware setup, improve logging and error handling, enhance the locale loading process, refactor the Onetime boot process, and remove unused methods and comments.

Fixes #471

---

PR Type

Enhancement, Bug fix, Documentation

---

Description

• Refactored middleware setup in config.ru for both development and production environments, simplifying the attachment logic.
• Set default log level to info for Logger in handle_invalid_percent_encoding and handle_invalid_utf8 middlewares.
• Refactored Onetime.boot! method for improved clarity and performance, extracting initialization steps into private methods and adding error handling.
• Removed legacy register_build CLI command and simplified the require_sudo method.
• Delayed requiring sentry-ruby until Sentry is enabled, improving initialization performance.
• Renamed BUILD.yml to VERSION.yml and updated version loading accordingly.
• Added new VERSION.yml file for versioning information.

---

Changes walkthrough 📝

	Relevant files
Enhancement	config.ru Refactor and simplify middleware setup in config.ru            config.ru Refactored middleware setup for development and production environments. Simplified middleware attachment logic. Moved require_relative 'lib/onetime' to a different position. +25/-36  handle_invalid_percent_encoding.rb Set default log level to info in handle_invalid_percent_encoding middleware lib/middleware/handle_invalid_percent_encoding.rb Set default log level to info for Logger. Added comment for check_enabled parameter. +2/-2      handle_invalid_utf8.rb Set default log level to info and log errors in handle_invalid_utf8 middleware lib/middleware/handle_invalid_utf8.rb Set default log level to info for Logger. Changed log level to error for invalid UTF-8 handling. +2/-2      onetime.rb Refactor Onetime.boot! method and improve initialization  lib/onetime.rb Refactored Onetime.boot! method for clarity and performance. Extracted initialization steps into private methods. Added error handling for boot process. Improved logging and configuration loading. +70/-60  cli.rb Remove legacy CLI command and simplify require_sudo method lib/onetime/cli.rb Removed legacy register_build CLI command. Simplified require_sudo method. +0/-10    config.rb Delay requiring sentry-ruby until enabled                                lib/onetime/config.rb Delayed requiring sentry-ruby until Sentry is enabled. Removed unnecessary require statement. +3/-3
Documentation	version.rb Rename BUILD.yml to VERSION.yml and update version loading lib/onetime/version.rb Renamed BUILD.yml to VERSION.yml. Updated version loading to use VERSION.yml. +1/-9      VERSION.yml Add VERSION.yml file for versioning information                    VERSION.yml Added new VERSION.yml file for versioning information. +5/-1

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-pro]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Key issues to review Middleware Setup The refactoring of middleware setup in development and production modes should be tested to ensure that the middleware behaves as expected in both environments. Logger Level The logger level is set to info which might not be suitable for all environments or use cases. Consider making this configurable or ensuring it aligns with the intended logging strategy. Error Handling The error handling in the boot! method uses generic rescue blocks which might suppress important error details. Consider logging more information or rethinking error handling strategy to avoid hiding issues.

[codiumai-pr-agent-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Refactor repeated Redis setup code into a method to enhance code organization Extract the repeated code for setting up the Redis connection into a separate method to reduce duplication and improve code organization. lib/onetime.rb [150-154] -16.times { |idx| - uri = Familia.redis.id - ping_result = Familia.redis(idx).ping - OT.ld "Connecting to #{uri} (#{ping_result})" -} +setup_redis_connections Apply this suggestion Suggestion importance[1-10]: 9 Why: Extracting repeated code for setting up Redis connections into a separate method reduces duplication and enhances code organization, making it easier to maintain and understand.	9
	Encapsulate error logging into a method for better error management Replace the direct logging of error messages with a method that encapsulates error handling to improve code modularity and error management. lib/middleware/handle_invalid_utf8.rb [129] -logger.error "[handle-invalid-utf8] #{message}" +log_error(message) Apply this suggestion Suggestion importance[1-10]: 8 Why: Encapsulating error logging into a method improves code modularity and makes error management more consistent and maintainable. This is a good practice for better error handling.	8
	Isolate Sentry setup into a dedicated method to enhance configuration modularity Move the Sentry setup into a dedicated method to isolate external service configuration and improve the modularity of the configuration code. lib/onetime/config.rb [55-59] -require 'sentry-ruby' -dsn = sentry[:dsn] -OT.info "[sentry-init] Initializing with DSN: #{dsn[0..10]}..." -Sentry.init do |config| +setup_sentry(sentry) Suggestion importance[1-10]: 8 Why: Moving the Sentry setup into a dedicated method isolates external service configuration, improving the modularity and readability of the configuration code. This enhances maintainability and clarity.	8
	Improve variable naming for clarity Consider using a more descriptive variable name than middlewares to enhance code readability. A name like configured_middlewares can make it clearer that this variable holds the middleware configurations based on the environment. config.ru [37] -middlewares = if Otto.env?(:dev) +configured_middlewares = if Otto.env?(:dev) Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion to rename middlewares to configured_middlewares improves code readability and maintainability by making the purpose of the variable clearer. However, it is a minor improvement and not crucial for functionality.	7