crimson/osd, seastore: fix log argument mismatches in error paths
two log calls in errorator continuations were missing an argument. the
compile-time fmt check surfaced these as a confusing "call to immediate
function ... is not a constant expression" deep in the errorator/composer
machinery rather than a plain "too few arguments", because the consteval
format failure escalates through the continuation templates:
- shard_services.cc handle_pg_create_info(): "ignore pgid {}" never
passed pgid.
- node.cc: the read_extent error handler logged "{} -- addr={},
is_level_tail={}" without the leading error; pass the std::error_code
and include <fmt/std.h> for its formatter.