Release 1.0.0

We're going to target the `1.0.0` release for Feb, after the final beta release (https://github.com/arcjet/arcjet-js/pull/5461) this week. In discussing whether we want to do the `1.0.0` release now, there were a few known issues / changes that might cause us to issue a "breaking" release. However, we decided that it was better to go to `1.0.0` now because of the benefits of the stable version number and because we don't know when these issues are going to be prioritized. The main issues discussed were: - https://github.com/arcjet/arcjet-js/issues/4214 - per @blaine-arcjet, rule constructors have to be async if the [entire rule is encapsulated in Wasm](https://github.com/arcjet/arcjet/issues/4745). Additionally, there are things we can't do right now, such as validating filters at rule construction (we also want to do other analysis, such as "needs body"). - https://github.com/arcjet/arcjet-js/issues/759 requires us to rewrite the ConnectRPC client. We will probably do this by implementing a lightweight minimum client that supports the features we need, whilst keeping the ConnectRPC server on our API. This may or may not be breaking. - Upcoming roadmap items for challenge support may be a `1.1.0` or may require a `2.0.0`. This is a major change that will require users to do work to adopt either way, so a version bump isn't a concern. Changes we want to land for 1.0.0: - https://github.com/arcjet/arcjet-js/pull/5578 - https://github.com/arcjet/arcjet-js/issues/5515 - https://github.com/arcjet/arcjet-js/issues/4477 - https://github.com/arcjet/arcjet-js/pull/5584 - https://github.com/arcjet/arcjet-js/pull/5589 - https://github.com/arcjet/arcjet-js/pull/5590 Changes requiring discussion to see if we can land for 1.0.0: - https://github.com/arcjet/arcjet-js/pull/5505 - https://github.com/arcjet/arcjet-js/pull/4753