[compute] Explicitly initialize dims_ in constructors to avoid uninitialized warnings

[ragmani]

This commit explicitly initialize dims_ in Shape constructors to avoid uninitialized warnings.

• Set dims_ using std::array or std::vector in the (int, int32_t), (int, const int32_t*), and initializer-list constructors to ensure proper initialization before calling Resize().
• Added a check in Resize() using dims_.valueless_by_exception() to handle any uninitialized state.

ONE-DCO-1.0-Signed-off-by: ragmani ragmani0216@gmail.com

[ragmani]

To fix the build error(#15030 (comment)), This PR addresses a problem where the Resize() function could access an uninitialized member (dims_). Unfortunately, modifying Resize() alone did not prevent the "maybe-uninitialized" warnings and I couldn't find other alternative approaches to avoid it, Therefore I updated some constructors to explicitly initialize dims_ using the correct alternative (std::array or std::vector) based on the dimensions count. Regrettably, these changes have made the Resize() function considerably longer than before.

[seockho-kim]

LGTM

[glistening]

I was reading the code before merging. Personally I don't like to merge this.

• It introduces duplicated code segments. I am not sure it is necessary.
• The code becomes more complicated and diverged from original code base, which was copied from tensorflow lite. At least, I don't understand the changed code.

As I wrote a few hours ago in #15157, I am investigating the reason, rather than rewriting and modifying the existing code to c++17. I expect the required change would be just a few lines or a few bytes.

[ragmani]

My priority is to ensure that the build doesn’t break, so for now, I'll implement fixes to avoid any build errors. Since I am only modifying the Shape class, if you're not happy with the changes, you can easily revert the modifications in the Shape file by replacing the file.