Rename Pico to Helidon Injection

[trentjeff]

Module Names

All modules names will replace "pico" with "inject".

• helidon-pico-project -> helidon-inject-project
• helidon-pico-api -> helidon-inject-api
• helidon-pico-configdriven-* -> helidon-inject-configdriven-*
• helidon-pico-maven-plugin -> helidon-inject-maven-plugin
• helidon-pico-processor -> helidon-inject-processor
• helidon-pico-runtime -> helidon-inject-runtime
• helidon-pico-testing -> helidon-inject-testing
• helidon-pico-tools -> helidon-inject-tools

Package Names

All package names will replace "pico" with "inject".

• io.helido.pico.* -> io.helidon.inject.*

Class Names

All package names will replace "Pico" with "Injection".

• PicoServices -> InjectionServices
• PicoServicesConfig -> InjectionServicesConfig
• PicoServicesHolder -> InjectionServicesHolder
• PicoException -> InjectionException
• ...

Method Names, Variable Names

All released artifacts will have all "pico" variables and methods changed to remove and/or replace the word "pico" in its name to a suitable alternative (i.e., "inject" or "injection", etc).

Configuration

• Currently "pico" is a reserved top-level configuration name. This name will be changed to "inject".
• All attributes with "pico" in the name will be replaced with "inject".

General

• All documentation (README, etc.) will rename "Pico" to either "Helidon Injection" for short, and in some cases "The Helidon Injection Framework".
• Some of these test modules and test names will leave "pico" in the names (these are not released in the bom)
  • tests/resources-pico

[trentjeff]

Blocked behind these PRs:

• Attempt to do type regeneration turned into an error condition instead of being logged #7155
• module-info parsing #7156
• Allow empty list injection #7160