Remove usage of deprecated VS Code Didact

[tdiesler]

Update generic languages, env, cron

[squakez]

Cool cleanup, thanks!

[squakez]

I think you forgot to swith resource-file-xyz examples. You've also removing resources-data files which were used by those examples.

[tdiesler]

I think you forgot to swith resource-file-xyz examples. You've also removing resources-data files which were used by those examples.

I removed it because I thought it was deprecated ...

## Configuration Resource file (Camel-K <= 1.12.1)

**These examples only work with a version of  Camel-K <= 1.12.1**

These examples show the different ways you can use **resource files** to configure integrations.

* provide properties from a resource file with `--config`
  * `config-file-route.groovy`

* provide properties from a resource file with `--resource`
* `resource-file-route.groovy`
* `resource-file-location-route.groovy`
* `resource-file-binary-route.groovy`
* `resource-file-base64-route.groovy`

Also when I try it I see ...

$ kamel run --resource file:resources-data.txt resource-file-route.groovy --dev
Error: could not match config or secret configuration as file:resources-data.txt

Are we expecting folks to load that file content in a configmap first?

Also, resources-data is not used in the camel-k/e2e tests (any more) either, but we have three data files for it. It may have slipped through the cracks and for parity we need to resurrect resource-file-xyz testing in both projects.

[camel-k]$ git grep resources-data
Binary file e2e/common/config/files/resources-data.zip matches

[tdiesler]

This commit removes resource-file-xyz.groovy route definitions without providing yaml equivalents. This was because none of the tests referenced those groovy files. Perhaps the examples provide close enough testing templates to resurrect resource-file testing.

We don't have --resource file:* (any more), only --resource configmap:* and --resource secret:*

[squakez]

This commit removes resource-file-xyz.groovy route definitions without providing yaml equivalents. This was because none of the tests referenced those groovy files. Perhaps the examples provide close enough testing templates to resurrect resource-file testing.

We don't have --resource file:* (any more), only --resource configmap:* and --resource secret:*

We don't need to have parity between tests and examples. Examples are typically more oriented to show basic or complex use cases for users. I think in this case we do need to convert the binary and base64 from groovy to yaml and moving also from file to configmap (if no other similar example is already available, of course) as it is a useful demo scenario to show.

[tdiesler]

I now migrated and restored all config/resource-file-xyz examples

With resource-file-base64-encoded-route.yaml I'm not sure about. --compression=true does not seem to do anything. The output is plain text as with resource-file-route.yaml

kamel run --dev --resource configmap:my-cm-file --compression=true resource-file-base64-encoded-route.yaml

[tdiesler]

This is ready to merge

[squakez]

I've just noticed something that would require some attention. We're missing to add some comment line to explain in the same example how to run it. For example, in the groovy example we used to have:

//
// To run this integrations use:
// 
// kubectl create configmap my-cm --from-literal=my-configmap-key="configmap content"
// kamel run --resource configmap:my-cm@/tmp/app/data resource-configmap-location-route.groovy --dev
//

And now we're missing it in the new example. I think we must bring this comment back in the new specific dsl format, of course.