docs: replace references to js-dataverse with current package naming

Author: g-saracca

.github/ISSUE_TEMPLATE/bug_report.md

@@ -6,7 +6,7 @@
 
 ## What did you expect to happen?
 
-## Which version of js-dataverse are you using?
+## Which version of dataverse-client-javascript are you using?
 
 ## Any related open or closed issues to this bug report?
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -4,6 +4,6 @@
 
 ## What existing behavior do you want changed?
 
-## Any brand new behavior do you want to add to js-dataverse?
+## Any brand new behavior do you want to add to dataverse-client-javascript?
 
 ## Any open or closed issues related to this feature request?

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Contributing to js-dataverse
+# Contributing to dataverse-client-javascript
 
 First of all thank you very much for your interest in contributing to this project!
 

package-lock.json

@@ -1,5 +1,5 @@
 {
-  "name": "js-dataverse",
+  "name": "@iqss/dataverse-client-javascript",
   "version": "2.0.0",
   "description": "Dataverse API wrapper package for JavaScript/TypeScript-based applications",
   "main": "./dist/index.js",

package.json

@@ -30,7 +30,7 @@ export const buildRequestConfig = (
       /*
         We set { withCredentials: true } to send the JSESSIONID cookie in the requests for API authentication.
         This is required, along with the session auth feature flag enabled in the backend, to be able to authenticate using the JSESSIONID cookie.
-        Auth mechanisms like this are configurable to set the one that fits the particular use case of js-dataverse. (For the SPA MVP, it is the session cookie API auth).
+        Auth mechanisms like this are configurable to set the one that fits the particular use case of dataverse-client-javascript. (For the SPA MVP, it is the session cookie API auth).
       */
       requestConfig.withCredentials = true
       break