Run clang-format in CI

[justinchuby]

Description

Run clang-format in CI. Formatted all c/c++, objective-c/c++ files.

Excluded

    'onnxruntime/core/mlas/**',
    'onnxruntime/contrib_ops/cuda/bert/tensorrt_fused_multihead_attention/**',

because they contain assembly or is data heavy

Motivation and Context

Coding style consistency

[edgchen1]

this is a generated file, can we exclude it?

[justinchuby]

I can exclude onnxruntime/core/flatbuffers?

[justinchuby]

Done

[edgchen1]

I can exclude onnxruntime/core/flatbuffers?

There are some other non-generated files there which we can still include.

[justinchuby]

Done

[edgchen1]

I think there may be some existing conventions for Java and C#, and also for WinML code.
@Craigacp @yuslepukhin @fdwr Are you all fine with these formatting changes?

[justinchuby]

Closing for now because I excluded them from this pr

[Craigacp]

The Java API has a code formatter called spotless that runs as part of the test suite, if you apply this one it'll get very confused and fail all the CI pipelines with Java in them.

[justinchuby]

Thanks for the info! I excluded java. Does the current change look good to you?

[Craigacp]

Yes, though the Java binding includes some C code with the extension .c. You could apply the formatter to that, we don't currently do any formatting on the C code for the Java binding.

[fdwr]

@justinchuby Did you intend to also rewrap enums?

Back when I was playing around with a half dozen formatters, I found this online clang formatter very quick and easy to try out different settings: https://zed0.co.uk/clang-format-configurator/

[justinchuby]

I think the rewrap was a side effect of clangformat seeing it has enough horizontal space to fit everything. I am going to consult with chatgpt

[justinchuby]

Couldn't figure it out with the configurator or with chatgpt. Do you have suggestions?

[justinchuby]

So we need a trailing comma.

[justinchuby]

chatgpt helpfully created a fix script: https://github.com/microsoft/onnxruntime/pull/15606/files

[justinchuby]

@edgchen1 Looks like there are potential build errors (not sure if it is flaky ci or true errors). Should I instead start from c++ then expand to other languages in separate prs? I will revert the subsequent changes

[edgchen1]

@edgchen1 Looks like there are potential build errors (not sure if it is flaky ci or true errors). Should I instead start from c++ then expand to other languages in separate prs? I will revert the subsequent changes

sure, that sounds good

[justinchuby]

Now just

'**/*.h',
'**/*.cc',
'**/*.hpp',
'**/*.cpp',
'**/*.m',
'**/*.mm',