feat: return deprecation warnings to users in yellow in colour.

[Peeeekay]

Description:

After this change - users can be notified about potential deprecated instructions/types/fields. It is abstracted away so that engineers can easily add relevant information for users to see. They also have ability to share other warning with users if need be.

Is this change user facing?

YES

References (if applicable):

[Peeeekay]

To add deprecation warning we can just do the following:

Deprecating an argument/field for instruction or type:-

KurtosisBaseBuiltin: &kurtosis_starlark_framework.KurtosisBaseBuiltin{
			Name: AddServiceBuiltinName,

			Arguments: []*builtin_argument.BuiltinArgument{
				{
					Name:              ServiceNameArgName,
					IsOptional:        false,
					ZeroValueProvider: builtin_argument.ZeroValueProvider[starlark.String],
				        Deprecation: starlark_warning.Deprecation(
			                          starlark_warning.DeprecationDate{Day: 20, Month: 11, Year: 2023},
			                         "Please use `xyx` field instead - for more info ...",
		                         ),

					Validator: func(value starlark.Value) *startosis_errors.InterpretationError {
						return builtin_argument.NonEmptyString(value, ServiceNameArgName)
					},
				},
			},
		},

The warning message will be: WARN: "service_config" field for "add_service" will be deprecated by 20/11/2023. mitigation reason

Deprecating an instruction or type:-

KurtosisBaseBuiltin: &kurtosis_starlark_framework.KurtosisBaseBuiltin{
			Name: AddServiceBuiltinName,
                         Deprecation: starlark_warning.Deprecation(
			          starlark_warning.DeprecationDate{Day: 20, Month: 11, Year: 2023},
			          "Please use `xyx` instruction instead - for more info ...",
		         ),
			Arguments: []*builtin_argument.BuiltinArgument{
				....
			},
		},

The warning message will be: WARN: "add_service" instruction will be deprecated by 20/11/2023. mitigation reason

[adschwartz]

@Peeeekay This looks good to me. My understanding is that this is the first PR. I see you have some todo's, are those meant for future work, or are those coming up in the next PR?

Either way this looks like a good first prototype.

[Peeeekay]

@adschwartz - those are future work which can be tackled as FLUPs - which I will create. They are not urgent but good to have.