[Profiler][inductor] put kwinputs in chrome traces

[davidberard98]

🚀 The feature, motivation and pitch

use case: inductor collects this info, and it would be great if we get this in the chrome traces since we already collect it.

proposal: start off just collecting string and integer inputs.

Here is where we use the non-kwarg inputs in profiler:

pytorch/torch/csrc/profiler/collection.cpp

Line 316 in be0eec9

torch_ops_.inputs_outputs_.push(fn.inputs());

I think this is where we put random metadata into kineto:

pytorch/torch/csrc/autograd/profiler_kineto.cpp

Line 248 in be0eec9

addMetadata("Input Dims", variantShapesToStr(arg_data.shapes));

it would be great if we can shove an arbitrary string->string dict into the op_event and then put it into the metadata in the profiler_kineto.cpp code

cc @robieta @chaekit @aaronenyeshi @guotuofeng @guyang3532 @dzhulgakov @briancoutinho @sraikund16 @sanrise @Chillee

Alternatives

No response

Additional context

No response