feat: Plugin Handling in Gateway

[Vinodsathyaseelan]

What

Add better Thunder plugin status handling in Gateway

Why

As a Ripple API Gateway component, Thunder Plugin activation and status needs to be managed by the Thunder broker.

How

Added a new component name ThunderStateManager. This will be used by Thunder Broker to check thunder plugin status.

Test

I have tested the features by running unit test cases

Checklist

• I have self-reviewed this PR
• I have added tests that prove the feature works or the fix is effective

[github-actions]

Package	Line Rate	Health
device.thunder_ripple_sdk.src.processors.events	0%	❌
device.thunder_ripple_sdk.src.processors	10%	❌
device.thunder_ripple_sdk.src.events	4%	❌
core.sdk.src.api.gateway	85%	✔
device.mock_device.src	52%	➖
core.main.src.bootstrap.manifest	0%	❌
core.main.src.state.cap	44%	➖
device.thunder_ripple_sdk.src.client	74%	➖
core.tdk.src.utils	0%	❌
device.thunder_ripple_sdk.src.bootstrap	0%	❌
distributor.general.src	2%	❌
core.sdk.src.extn	83%	✔
device.thunder_ripple_sdk.src	15%	❌
core.sdk.src.api.manifest	91%	✔
core.main.src	0%	❌
core.sdk.src.framework	75%	➖
core.main.src.broker	21%	❌
core.main.src.utils	10%	❌
core.main.src.broker.thunder	55%	➖
core.tdk.src.gateway	100%	✔
core.main.src.service.apps	47%	➖
device.thunder.src.bootstrap	0%	❌
core.launcher.src	0%	❌
openrpc_validator.src	90%	✔
core.sdk.src.api.device	77%	✔
core.main.src.bootstrap.extn	0%	❌
core.main.src.bootstrap	0%	❌
core.launcher.src.manager	7%	❌
core.sdk.src.extn.ffi	80%	✔
core.main.src.service	31%	❌
core.main.src.processor	0%	❌
core.sdk.src.utils	53%	➖
core.sdk.src.extn.client	91%	✔
core.main.src.firebolt.handlers	1%	❌
core.main.src.processor.storage	0%	❌
core.sdk.src.api.firebolt	78%	✔
core.main.src.firebolt	1%	❌
core.main.src.service.extn	41%	❌
core.sdk.src.api.distributor	84%	✔
device.thunder.src	0%	❌
core.sdk.src.api	78%	✔
core.sdk.src.api.observability	68%	➖
core.main.src.state	22%	❌
Summary	42% (16763 / 39476)	➖

Minimum allowed line rate is 41%