### Motivation

*Compatible with flink 1.11 need to use java8 date api in pulsar's primitive schemas.*

### Modifications

*Add Instant, LocalDate, LocalTime, LocalDateTime to pulsar's primitive schemas*

### Verifying this change

Add Instant, LocalDate, LocalTime, LocalDateTime types to the Schema type test

### Motivation

After upgrade to Apache Avro 1.9.x, the default time conversion changed to JSR-310. For forwarding compatibility, we'd better add the Joda time conversion.

related to #5938 

### Modifications

Add joda time conversions

### Verifying this change

New integration test added

### Motivation

Currently, Pulsar uses Avro 1.8.2, a version released two years ago. The latest version of Avro is 1.9.1, which uses FasterXML's Jackson 2.x instead of Codehaus's Jackson 1.x. Jackson is prone to security issues, so we should not keep using older versions.
https://blog.godatadriven.com/apache-avro-1-9-release

### Modifications

Avro 1.9 has some major changes:

- The library used to handle logical datetime values has changed from Joda-Time to JSR-310 (https://github.com/apache/avro/pull/631)
- Namespaces no longer include "$" when generating schemas containing inner classes using ReflectData (https://github.com/apache/avro/pull/283)
- Validation of default values has been enabled (https://github.com/apache/avro/pull/288). This results in a validation error when parsing the following schema:
```json
{
  "name": "fieldName",
  "type": [
    "null",
    "string"
  ],
  "default": "defaultValue"
}
```
The default value of a nullable field must be null (cf. https://issues.apache.org/jira/browse/AVRO-1803), and the default value of the field as above is actually null. However, this PR disables the validation in order to maintain the traditional behavior.

* Change import org.apache.pulsar.common.policies.data.SchemaCompatibilityStrategy;

* Schema compatibility check change

* Add the test

* modify the cmdNamespaces

* Modify the variable name

* Delete the configuration

* Modify the variable name

* modify the method

* Fix some tests

* add the integration test

* Modify the test

* modity the Timeout time

* Modify the test's sequence

* modify the exception message

* Add the test

* modify the httpLookupService

* Add the license

* add the method

* Modify decode message throw exception

* Add the import class

* fix some comment

* Modify the implments method

* add the judgement for consumer schema compatibility check

* add the import

### Motivation
To fix #4831

### Motivation
To fix #4838 

* [schema] Fix joda dependency issue.

* [schema] Add binary license of joda-time.

* [schema] Make joda-time dependency optional.

* [schema] Change log level to debug for logical type init.

* [schema] fix joda-time license in presto distribution

* [schema] fix joda-time license in presto distribution

### Motivation

Fix #3742

In order to decode the message correctly by AVRO schema, we need to know the schema what the message is.

### Modification

- Introduced Schema Reader and Schema Writer for StructSchema.
   - Reader is used to decode message
   - Writer is used to encode message
- The implementations of StructSchema, provides their schema reader and writer implementations. 
- Introduced a schema reader cache for caching the readers for different schema versions. 

Fixes #3211
Fixes #2786 

*Motivation*

When a schema is deleted, the schema is not removed directly.
You can still fetch the latest schema but its state is marked as `deleted`.

So when we apply schema compatibility check, we should ignore deleted schema.

*Modifications*

Ignore deleted schema when doing schema compatibility check