Log non-pt2_compliant ops encountered by Dynamo

Summary:
X-link: pytorch/pytorch#112581

See internal diff for more changes. Whenever we encounter a non-compliant op,
we add it to a set on the OutputGraph. When a compilation event happens, we log
the contents of this set.

I'm planning on flipping the `only_allow_pt2_compliant_ops` config from False
to True after the logging determines that existing models do not use
non-compliant ops.

Reviewed By: yanboliang

Differential Revision: D50884828

fbshipit-source-id: 9866322c19b6b5cf702ac8b2afb2f450f0b9b438

Author: zou3519

userbenchmark/dynamo/dynamobench/_dynamo/utils.py

@@ -28,7 +28,7 @@
 from contextlib import contextmanager
 from functools import lru_cache, wraps
 from pathlib import Path
-from typing import Any, Dict, Optional, Tuple, Union
+from typing import Any, Dict, Optional, Set, Tuple, Union
 
 try:
     import numpy as np
@@ -556,6 +556,7 @@ class CompilationMetrics:
     entire_frame_compile_time_s: Optional[float]
     backend_compile_time_s: Optional[float]
     fail_reason: Optional[str]
+    non_compliant_ops: Set[str]
 
 
 @dataclasses.dataclass