Fix inconsistent timestamp format in groups_spec.rb test expectations

[Copilot]

Test expectations in groups_spec.rb used inconsistent timestamp conversion formats, mixing (@time_now.to_f * 1000).to_i (millisecond-preserving) with @time_now.to_i * 1000 (millisecond-truncating).

Changes

• Standardized all 9 inconsistent test expectations to use (@time_now.to_f * 1000).to_i
• Affected tests: properly cast dates, convert offset datetimes to UTC, convert offset ActiveSupport::TimeWithZone, set_once, remove, union, unset (both variants), and delete_group

# Before (loses millisecond precision)
'$time' => @time_now.to_i * 1000

# After (preserves millisecond precision, consistent with line 26)
'$time' => (@time_now.to_f * 1000).to_i

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• http://index.rubygems.org:80/api/v1/dependencies
  • Triggering command: /home/REDACTED/.local/share/gem/ruby/3.2.0/bin/bundle bundle install (http block)
• http://index.rubygems.org:80/versions
  • Triggering command: /home/REDACTED/.local/share/gem/ruby/3.2.0/bin/bundle bundle install (http block)
• http://rubygems.org:80/specs.4.8.gz
  • Triggering command: /home/REDACTED/.local/share/gem/ruby/3.2.0/bin/bundle bundle install (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)