Replace std::vector with uint64_t bitset in WebRequestMethodComposite

[Copilot]

WebRequestMethodComposite used std::vector<WebRequestMethod> internally, causing heap allocations and fragmentation on embedded targets. The question was raised whether a uint64_t bitset would limit the method set to only 8 values.

Changes

• Allocation-free storage: Replace std::vector<WebRequestMethod> with uint64_t _bits (one bit per http_method index) + bool _any for the HTTP_ANY (= 255) sentinel. The entire object is now 9 bytes with no heap involvement.
• Capacity: A 64-bit bitmask supports indices 0–63. The http_method enum currently defines 34 values (0–33), so all methods fit with room to spare — not 8.
• HTTP_ANY handling: Stored separately as bool _any; allows(HTTP_ANY) explicitly returns false (it is not a real request method, only a match-all sentinel).

// Before: heap-allocating list
std::vector<WebRequestMethod> _methods;

// After: 9-byte allocation-free bitset
uint64_t _bits;   // bit i set → method (http_method)i is allowed
bool _any;        // true → match any method (HTTP_ANY sentinel)

All public semantics (allows, operator==, operator|, operator&, empty, toString) are preserved.

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.