fix: Performance bug fix to emit marks for only first tab

[guptbhum]

Description

Bug - {component}Rendered and {component}Updated marks are emitted even if current component is adding to the second tab component. We don't want to publish metrics for the sections which are not visible on page load.
Fix - Updated the usePerformanceMarks logic to emit markers only if the primary button or table is added to the first tab.

Related links, issue #, if available: n/a

How has this been tested?

Locally tested the change
TODO - Updated unit and integration tests

Review checklist

The following items are to be evaluated by the author(s) and the reviewer(s).

Correctness

• Changes include appropriate documentation updates.
• Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
• Changes do not include unsupported browser features, see CONTRIBUTING.md.
• Changes were manually tested for accessibility, see accessibility guidelines.

Security

• If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

• Changes are covered with new/existing unit tests? existing tests
• Changes are covered with new/existing integration tests? existing tests

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

Attention: Patch coverage is 92.30769% with 1 line in your changes missing coverage. Please review.

Project coverage is 96.39%. Comparing base (67c06fa) to head (73385d3).
Report is 6 commits behind head on main.

Files with missing lines	Patch %	Lines
src/internal/hooks/use-performance-marks/index.ts	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3182      +/-   ##
==========================================
- Coverage   96.40%   96.39%   -0.02%     
==========================================
  Files         784      785       +1     
  Lines       22144    22154      +10     
  Branches     7191     7192       +1     
==========================================
+ Hits        21349    21356       +7     
- Misses        788      791       +3     
  Partials        7        7              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[connorlanigan]

The first enabled tab is not necessarily the tab that is initially open, because developers can control which tab they want to show initially using the activeTabId prop. I recommend to store the initial value of the activeTabId variable, and use that to determine whether the Tabs component is still showing the initial tab, until the user switches tabs for the first time.

For example, something roughly like:

const [activeTabId, setActiveTabId] = useControllable(...);

const initialTabId = useState(activeTabId)[0];

const isOnInitialTab = useRef(true);

if(isOnInitialTab.current) {
   isOnInitialTab.current = activeTabId === initialTabId;
}

...


<TabContext.Provider
     value={{
       isInInitialTab: isOnInitialTab.current,
     }}
   >

[orangevolon]

I think this is a left-over.

[orangevolon]

I'd suggest to change this to isInDefaultTab or hasTabChanged. First tab means the first one from the left and the default tab might not be that one.

[orangevolon]

We have changed !enabled() to enabled. Is this on purpose?

The type of enabled is still function.

components/src/internal/hooks/use-performance-marks/index.ts

Line 44 in e1c488b

enabled: () => boolean,