Standardize name for LLM comps

[XinyaoWa]

Description

Update all the names for classes and files in llm comps to follow the standard format

Issues

#998

Type of change

List the type of change like below. Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would break existing design and interface)
• Others (enhancement, documentation, validation, etc.)

Dependencies

no

Tests

tests/llm/*.sh

[eero-t]

Update all the names for classes and files in llm comps to follow the standard format

@XinyaoWa Which standard format that is?

Neither this PR description, nor files it changes, contains a link to any specific standard, or rules being followed in naming.

The result seems rather inconsistent:

GenAIComps$ git grep -h OpeaComponentRegistry.register | grep -e DocSum -e TextGen -e DATA
@OpeaComponentRegistry.register("OPEA_DATAPREP_MILVUS")
@OpeaComponentRegistry.register("OPEA_DATAPREP_REDIS")
@OpeaComponentRegistry.register("OpeaDocSumTgi")
@OpeaComponentRegistry.register("OpeaDocSumvLLM")
@OpeaComponentRegistry.register("OpeaTextGenNative")
@OpeaComponentRegistry.register("OpeaTextGenPredictionguard")
@OpeaComponentRegistry.register("OpeaTextGenService")

• some names are all caps with underlines, some use CamelCase without any underlines
• Some items are capitalized (."..Tgi"), some are the opposite of it ("...vLLM"), even in same component (DocSum)
• Some items have backend name as suffix (DataPrep & DocSum), others something else ("OpeaTextGenService")

PS. IMHO "OpeaDocSum_TGI" / "OpeaDocSum_vLLM" were more reasonable and readable names than the new ones. Earlier suffix matched backend's official name, and was clearly separated from application / use-case prefix.