Mark request builder getters deprecated if all their child methods are too

Is your feature request related to a problem? Please describe the problem.

While testing different API specs, I noticed that some contain deprecated endpoints. That in itself is propagated through deprecation annotations in every language.

However, since Kiota builds a class structure around the URL paths, it should recursively mark request builders as deprecated, if all of their endpoints and child request builders are deprecated.

For example:

Say, I have an endpoint /packages/{package}/version/{version}.tar.gz. It is marked deprecated.

In generated code, you'd have a hierarchy like:

ApiClient                                             
  .packages ───────► PackagesRequestBuilder           
    .byPackage() ──► WithPackageItemRequestBuilder    
      .versions ───► VersionsRequestBuilder           
        .withVersionTarGz() ◄─ only this is marked "deprecated"

Now let's also say this is the only endpoint under /packages/.

It wouldn't make sense to only mark withVersionTarGz as deprecated, right?

Client library/SDK language

None

Describe the solution you'd like

I'd like Kiota to check if all endpoints in any given request builder are deprecated, mark it deprecated and repeat the whole process one layer above.

This way, all paths that are deprecated are marked as such, as opposed to only the final methods (or leaf nodes).

Additional context

No response

No source file, test, or entry point is named. Start by tracing how Kiota propagates deprecation annotations while generating request-builder hierarchies, then identify where child endpoints and builders are evaluated. Done means a request builder is marked deprecated when all its endpoints and child builders are deprecated, with that result recursively propagated upward.