Skip dynamic component generation if the version is available statically

[Revolyssup]

Signed-off-by: ashish ashishjaitiwari15112000@gmail.com

Description

Currenly dynamic component generation takes place , no matter what. If we already have components for that version statically then we can skip that operation as it is costly(because it executes kubeopenapi-jsonschema binary)

Notes for Reviewers
Since we are making use of the versioning, the directory in which all definitions and schemas reside should be named properly. The name will be the version.

Signed commits

• Yes, I signed my commits.

[Revolyssup]

@Utkarsh-pro Before you point out that why are we loading in the init function of that package. That package is imported here only for component registration so we are sure that if this package gets imported, comp reg is gonna take place. So I see no harm. Your insights would be valuable.
If you see any problem in this approach, I will abort it. Otherwise, will make same change across all adapters.
// @leecalcote

[tangledbytes]

LGTM

[tangledbytes]

@Utkarsh-pro Before you point out that why are we loading in the init function of that package. That package is imported here only for component registration so we are sure that if this package gets imported, comp reg is gonna take place. So I see no harm. Your insights would be valuable. If you see any problem in this approach, I will abort it. Otherwise, will make same change across all adapters. // @leecalcote

@Revolyssup, this looks good. I think we have seen a similar pattern in kubectl auth plugins source code (I may be wrong here), right?