Upgrade Graph SDK version to v2.29.1

[KenitoInc]

No description provided.

[learn-build-service-prod]

Learn Build status updates of commit 94e1216:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
	❌Error		Details

• Line 0, Column 0: [Error: PSMD2Yaml_FileLoadFailed] Failed to load file: C:/LocalRun/W/ilve-s/module/mapping/monikerMapping.json. PackageRoot, ReferenceTocUrl, and ConceptualTocUrl are required for every moniker. PackageRoot should be a valid relative path to docset root.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[SamErde]

I've been thinking about submitting this same PR but have minor reservations because there doesn't seem to be a release of the Graph module since 2.25.0 that has no roadblock issues for some users. It would be ideal if we could set a minimum version of this dependency, declare incompatibility with specific versions (2.26.0, 2.26.1), and allow other newer versions. I believe this can be done with Nuget package specifications but not a PowerShell module manifest.

One possible approach that I was thinking about was to change the manifest from 'RequiredVersion' to 'MinimumVersion' and then add a function to Microsoft.Entra that warns if the user is running an unsupported version of Microsoft.Graph. This check could easily be added to Connect-Entra or the manifest's ScriptsToProcess attribute. This approach would allow people to remain on Microsoft.Graph 2.25.0 if they need to or upgrade to 2.29.1 if they need a newer version.