refactor(react-framework): update possible null and undefined

[odinr]

Why

improve handling of possible null and undefined

Check off the following:

• Confirm that I checked changes to branch which I am merging into.

  • I have validated included files
  • My code does not generate new linting warnings
  • My PR is not a duplicate, check existing pr`s

• Confirm that the I have completed the self-review checklist.

• Confirm that my changes meet our code of conduct.

Conditional

• Confirm project selected and category, actual, iteration are set
• Confirm Milestone selected (if any)

[changeset-bot]

🦋 Changeset detected

Latest commit: a99ade8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 8 packages

Name	Type
@equinor/fusion-framework-react	Patch
@equinor/fusion-framework-cli	Patch
@equinor/fusion-framework-react-app	Patch
@equinor/fusion-framework-react-components-bookmark	Patch
@equinor/fusion-framework-react-components-people-provider	Patch
@equinor/fusion-framework-legacy-interopt	Patch
@equinor/fusion-framework-react-module-bookmark	Patch
@equinor/fusion-framework-cookbook-app-react-feature-flag	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	4.8%	1288 / 26792
🔵	Statements	4.8%	1288 / 26792
🔵	Functions	5.99%	41 / 684
🔵	Branches	14.52%	106 / 730

File Coverage

File	Stmts	% Branch	% Funcs	% Lines	Uncovered Lines
Changed Files
packages/react/framework/src/app/useCurrentApp.ts	0%	0%	0%	0%	1-38
packages/react/framework/src/app/useCurrentAppModule.ts	0%	0%	0%	0%	1-45
packages/react/framework/src/app/useCurrentAppModules.ts	0%	0%	0%	0%	1-44

Generated in workflow #3867